* [ECOS] private header files unaccessible from package dirs
@ 2005-10-07 15:36 Heiko Panther
2005-10-07 17:32 ` Andrew Lunn
0 siblings, 1 reply; 2+ messages in thread
From: Heiko Panther @ 2005-10-07 15:36 UTC (permalink / raw)
To: ecos-discuss
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
my package sources are organized into several subdirectories, and I also want to
put private headers into a subdir. However, the compiler is set up to only look
in the source files directory, and the public header directory. What do you
recommend to make the private headers available? I don't wannt to have to prefix
my include files like
#include "pinclude/myheader.h"
and I also don't want to export my privates.
Best,
Heiko
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkNGlgEACgkQnbN38ql/gmDPMgCg+EsoPw5eJTOS+UA8ZRMT3mxa
WNYAnROatdyF/o7UxuFjmppyXndKJWYf
=i1rK
-----END PGP SIGNATURE-----
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ECOS] private header files unaccessible from package dirs
2005-10-07 15:36 [ECOS] private header files unaccessible from package dirs Heiko Panther
@ 2005-10-07 17:32 ` Andrew Lunn
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Lunn @ 2005-10-07 17:32 UTC (permalink / raw)
To: Heiko Panther; +Cc: ecos-discuss
On Fri, Oct 07, 2005 at 08:36:33AM -0700, Heiko Panther wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi there,
> my package sources are organized into several subdirectories, and I also want to
> put private headers into a subdir. However, the compiler is set up to only look
> in the source files directory, and the public header directory. What do you
> recommend to make the private headers available? I don't wannt to have to prefix
> my include files like
> #include "pinclude/myheader.h"
> and I also don't want to export my privates.
You can add addition compiler flags using
cdl_option CYGPKG_forbar_CFLAGS_ADD
eg jffs2 has
cdl_option CYGPKG_FS_JFFS2_CFLAGS_ADD {
display "Additional compiler flags"
flavor data
no_define
# We add '-D__ECOS' to trigger eCos-specific code in places.
# We add '-nostdinc -iwithprefix include' to avoid picking up
# native <linux/*.h> include files when building on Linux.
default_value { "-D__ECOS -nostdinc -iwithprefix include" }
description "
This option modifies the set of compiler flags for
building the JFFS2 package.
These flags are used in addition
to the set of global flags."
}
So doing something like
default_value { "-I$(REPOSITORY)/$(PACKAGE)/src/include" }
might work.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-10-07 17:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-10-07 15:36 [ECOS] private header files unaccessible from package dirs Heiko Panther
2005-10-07 17:32 ` 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).