From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>
Subject: Re: [ptxdist] Building a kernel module with special build script
Date: Mon, 24 Aug 2015 11:17:43 +0200 [thread overview]
Message-ID: <201508241117.43468.jbe@pengutronix.de> (raw)
In-Reply-To: <895ec2aa2b794b4ba0e7e1b5f2cc891b@GINS-EXC01.gins.local>
Hi Jan-Marc,
On Friday 14 August 2015 14:14:42 Stranz Jan-Marc wrote:
> in a bsp project I've to build a very special kernel module ("SysLink" from
> TI).
>
> In order to build this syslink.ko kernel module I have to install
> additional tools from TI. This can be assumed as an preparation step and
> have do bee done once manually before building the bsp project.
>
> For building the syslink.ko kernel module I have to invoke 'make' with a
> some parameters:
>
> make DEVICE=OMAPL1XX \
> SDK=NONE \
> DEPOT==$(PTXDIST_WORKSPACE)/local_src/syslink-2_21_03_11/depot/ \
>
> LINUXKERNEL=$(PTXDIST_PLATFORMDIR)/build-target/linux-$(KERNEL_VERSION)/ \
> CGT_ARM_PREFIX=$(PTXDIST_TOOLCHAIN)/$(PTXCONF_GNU_TARGET) \
> IPC_INSTALL_DIR=/opt/ti/ipc_1_25_03_15/ \
> BIOS_INSTALL_DIR=/opt/ti/bios_6_34_04_22/ \
> XDC_INSTALL_DIR=/opt/ti/xdctools_3_24_05_48/ \
> CGT_C674_ELF_INSTALL_DIR=/opt/ti/ti-cgt-c6000_8.0.3/ \
> syslink
>
> How can this be included in appropriate manner in a user defined rule?
> I would need help to create a file "rules/syslink.make" that can be
> integrated in the existing bsp project.
Do you know "ptxdist newpackage kernel"?
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-08-24 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 12:14 Stranz Jan-Marc
2015-08-24 9:17 ` Juergen Borleis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201508241117.43468.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=JM.Stranz@gantner-instruments.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox