Hi Caolanm/Stephan, Ugly works for me - no issues. Please bear with while I try to understand this.
I have a makefile from Simple Calc example. It uses cppumaker to generate some header files from my idl files. I think you are saying Xdesktop/XEnumerationAccess are genrated in that step. That works and I understand it now. I don't understand what you said about " if you built an example, they are generated". I thought they depend on my idl or are they buildable before I start writing any uno code? Once they are generated, I need to specify those paths in -I <include> for the _impl.o One option is - I know where they are and I can explicitly include those paths. But I am wondering if they are put in any of the standard paths - by standard path I mean those dir which are set by the sdk env script (setsdkenv_unix.sh). At this stage of learning, I would like to avoid including another make file to let things work magically. The makefiiles in examples were too complicated for me so I prefer stick with the one that comes with Simple Calc example. But I don't see any standard path pointing to libreoffice-4.0.0.3/workdir. Nor do I see those dir specified as args to cppumaker. I am wondering how cppumaker decides where to generate the headers. Once it knows about libreoffice-4.0.0.3/workdir, it also decides about a few other dirs: e.g. offapi and udkapi. How does it get those names ? If it is from env, I can use it in my make. If it is hardcoded, that is fine too - I can hardcode it in my make. thx Neeraj > >
Makefile
Description: Binary data
setenv
Description: Binary data
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
