On 08/01/2010 14:39, Richard Whitehead wrote:
> Hello,
> 
> Please can someone help with the basics of adding some code to the OOo 
> source.
> 
> I am using a third-party static library that I want to call from the 
> existing code.  I added my new source code (to an existing OOo source file 
> at present) and added a #include to the library's header.  It compiled but 
> would not link, as expected.  I then modified the makefile to link to the 
> library.  But now on the second build it won't compile!  It is saying 
> "library/include/library.h not found, and can't be made".
> 
> Even more bizarely, if I change the path in the #include statement, the 
> error message is not changing - so something has cached it?
> 
> Presumably some system has parsed the source code and found my header and 
> now wants to compile something?  How do I stop it from doing this?  I just 
> want to include
> a header and call a library, it can't be that hard?

there is dependency tracking for included files in the build system.
if you remove or rename an included file, then this can happen.
you can then manually regenerate the dependencies via "build depend=t".
in current milestones depend=t is broken; as a workaround just delete
$INPATH/misc/* in the offending module (INPATH is e.g. unxlngi6.pro/wntmsci12).

> T rebuild, I am changing directory to the MODULE I'm altering, then doing 
> the following, as specified in the "compatible build" section of the 
> "building on windows" help:
> build --from MODULE --prepare
> build && deliver
> 
> Please can someone help, I have not succeeded in making a single compilable 
> change to the source code yet!
> 
> Many thanks,
> 
> Richard 

regards, michael

-- 
>From the Plan 9 FAQ:
Q: Where did the name come from?
A: It was chosen in the Bell Labs tradition of selecting
   names that make marketeers wince.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Reply via email to