* [ECOS] how to control header file inclusion ?
@ 2003-09-20 6:23 rakesh
2003-09-20 12:17 ` Gary Thomas
0 siblings, 1 reply; 4+ messages in thread
From: rakesh @ 2003-09-20 6:23 UTC (permalink / raw)
To: ecos-mailing-list
I have added a new package(as cdl_package) to ecos
repository. Inside the package source, I have three
directories; cdl, include and src. Direcory src have
source files for three modules(as cdl_component),
which will be compiled if corrosponding module in
enabled in configtool. Directory include have header
files for all modules. But regardless of any module
enabled or disabled, it's header files will be present
in ecos_install/include direcoty(my build directory).
In cdl script, I can control source file compilation
depending upon if module is enabled. But how to
control include files? I tried to put include_dir
option in cdl_component but that complains.
Documentation also says that include_dir and
include_files can be put into cdl_package only. I
don't want to see lot of unnecessary header files in
ecos_install/include directory. Can I specify any
header file directory path in cdl?
Regards
Rakesh
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] how to control header file inclusion ?
2003-09-20 6:23 [ECOS] how to control header file inclusion ? rakesh
@ 2003-09-20 12:17 ` Gary Thomas
2003-09-21 2:23 ` rakesh
0 siblings, 1 reply; 4+ messages in thread
From: Gary Thomas @ 2003-09-20 12:17 UTC (permalink / raw)
To: rakesh; +Cc: eCos Discussion
On Sat, 2003-09-20 at 00:23, rakesh wrote:
> I have added a new package(as cdl_package) to ecos
> repository. Inside the package source, I have three
> directories; cdl, include and src. Direcory src have
> source files for three modules(as cdl_component),
> which will be compiled if corrosponding module in
> enabled in configtool. Directory include have header
> files for all modules. But regardless of any module
> enabled or disabled, it's header files will be present
> in ecos_install/include direcoty(my build directory).
> In cdl script, I can control source file compilation
> depending upon if module is enabled. But how to
> control include files? I tried to put include_dir
> option in cdl_component but that complains.
> Documentation also says that include_dir and
> include_files can be put into cdl_package only. I
> don't want to see lot of unnecessary header files in
> ecos_install/include directory. Can I specify any
> header file directory path in cdl?
>
If you don't want the include files exported (placed into the
build tree), then just don't put them in your "include" directory!
There's nothing against having include files in the "src" directory.
These files would then only be accessible by the local package,
which is what you're looking for I believe.
As for using the CDL directives, look for a working example, such as:
devs/wallclock/dallas/ds1742/current/wallclock_ds1742.cdl
This package chooses to place its include files in <cyg/io/wallclock/...>
and explicitly decides which files to export.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] how to control header file inclusion ?
2003-09-20 12:17 ` Gary Thomas
@ 2003-09-21 2:23 ` rakesh
2003-09-21 8:40 ` Andrew Lunn
0 siblings, 1 reply; 4+ messages in thread
From: rakesh @ 2003-09-21 2:23 UTC (permalink / raw)
To: Gary Thomas; +Cc: eCos Discussion
>
> If you don't want the include files exported (placed
> into the
> build tree), then just don't put them in your
> "include" directory!
> There's nothing against having include files in the
> "src" directory.
> These files would then only be accessible by the
> local package,
> which is what you're looking for I believe.
Probably I could not convey my problem. I want to
export header files but only if needed. Say if a
module in my source is selected by configtool then
only it's headers should be exported otherwise not.
Can I do this?
Regards
Rakesh
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ECOS] how to control header file inclusion ?
2003-09-21 2:23 ` rakesh
@ 2003-09-21 8:40 ` Andrew Lunn
0 siblings, 0 replies; 4+ messages in thread
From: Andrew Lunn @ 2003-09-21 8:40 UTC (permalink / raw)
To: rakesh; +Cc: Gary Thomas, eCos Discussion
> Probably I could not convey my problem. I want to
> export header files but only if needed. Say if a
> module in my source is selected by configtool then
> only it's headers should be exported otherwise not.
> Can I do this?
I don't think you can.
What you need to do is split your code up into a number of separate
packages. Each package can then be enabled/disabled as needed so
exporting/not exporting its header files as needed.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-09-21 8:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-20 6:23 [ECOS] how to control header file inclusion ? rakesh
2003-09-20 12:17 ` Gary Thomas
2003-09-21 2:23 ` rakesh
2003-09-21 8:40 ` Andrew Lunn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).