[okl4-developer] FW: Adding Software to OKL4
Geoffrey Lee
glee at ok-labs.com
Mon Aug 11 15:40:31 EST 2008
On Fri, Aug 08, 2008 at 11:18:08AM +0200, Frank Kaiser wrote:
>
> The missing header files were not copied from their original location
> which is 'cust/okl/libs/l4/cust/include'. Another file located there is
> 'vregs_asm.h'. What has happened is that the explicit assignment
> 'CUST=<cust>' overwrites the default assignment 'CUST="okl"' which is
> represented by line 478 of 'projects/iguana/SConstruct'. With CUST not
> being assigned to "okl" the build script 'libs/l4/SConscript' does not
> correctly extend the public headers (line 89 to 92):
>
> public_headers = [("include/", "include/l4/"),
>
> (os.path.join(arch_path, "include", ""),
> "include/l4/arch/"),
>
> (os.path.join(cust_path, "include", ""),
> "include/l4/cust/")
>
> ]
>
> This leads to the effective path 'cust/<cust>/libs/l4/cust/include', so
> that the 2 header files cannot be found. This is clearly inconsistent:
> on one side allowing a variable 'cust_path', on the other side having
> something which only works with a predefined value. I wonder what at all
> is the benefit of having header files required by the L4 library in that
> CUST location?
Hi Frank
This scheme is required to support some local modifications for folks
that require their code to be diverged away from the main OKL
code. If you make use of the cust feature you should be prepared
to supply your own local copies of those files. A short workaround if
you need to make use of the cust feature may be to copy the libl4
header files to your own cust directory.
-gl
>
>
>
> Regards
>
> Frank
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
--
More information about the Developer
mailing list