I think I get it now. I didn't realize earlier and I had to generate headers for system UNO types.<div>The sample Makefile - it seems - was assuming they were generated, so -T was specified</div><div>to generate the new ones.</div>
<div>Once I removed the -T to generate all, both the headers XEnumerationAccess/XDesktop</div><div>were generated.</div><div>Also, the sample Makefile I was using, didn't not specify -O so the output was going to current dir. The next steps were including -I. to pick it up.</div>
<div>This is not ideal, but for now, it helps me understand.</div><div>When I have more than 1 project, the system UNO types can all go in common dir and generated once. And this perhaps what <a href="http://stdtarget.mk">stdtarget.mk</a> is trying to acheive via SDKTYPEFLAG.<br>
<div><div>One last question - can I generate the system UNO types once per box, may be after SDK installation?</div><div><br></div><div>thanks</div><div>Neeraj</div><div><br><div class="gmail_quote">On Fri, Mar 8, 2013 at 3:56 AM, Stephan Bergmann <span dir="ltr"><<a href="mailto:sbergman@redhat.com" target="_blank">sbergman@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 03/08/2013 01:16 AM, Neeraj Rai wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a makefile from Simple Calc example. It uses cppumaker to<br>
generate some header files from my idl files. I think you are saying<br>
Xdesktop/XEnumerationAccess are genrated in that step. That works and I<br>
understand it now.<br>
</blockquote>
<br>
No. An invocation of cppumaker only generates the header files corresponding to those UNO types you tell it to. So your makefile's invocation of cppumaker will presumably only generate header files corresponding to your newly introduced .idl files.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't understand what you said about " if you built an example, they<br>
are generated".<br>
I thought they depend on my idl or are they buildable before I start<br>
writing any uno code?<br>
</blockquote>
<br>
So this part is about the UNO types that ship with the SDK.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Once they are generated, I need to specify those paths in -I <include><br>
for the _impl.o<br>
One option is - I know where they are and I can explicitly include those<br>
paths.<br>
But I am wondering if they are put in any of the standard paths -<br>
by standard path I mean those dir which are set by the sdk env script<br>
(setsdkenv_unix.sh).<br>
</blockquote>
<br>
Where the header files are generated to is specified in the call to cppumaker. The header file for the standard UNO types generated via that rule in the SDK's settings/<a href="http://stdtarget.mk" target="_blank">stdtarget.mk</a> are generated to $(OUT_INC) as defined in settings/<a href="http://std.mk" target="_blank">std.mk</a>.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But I don't see any standard path pointing to libreoffice-4.0.0.3/workdir.<br>
</blockquote>
<br>
By design, the SDK never points into a LO build's workdir or solver. It only points at parts of a LO installation.<br>
<br>
But, to get your own local makefile experiments started, it can be easier to "cheat" and re-use the header files generated for the standard UNO types there, in solver/*/inc/udkapi and solver/*/inc/offapi (so you would need to add two -I flags).<span class="HOEnZb"><font color="#888888"><br>
<br>
Stephan<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>=====<br>Intuition - is the inability to figure out the facts on which we based the decision. <br>
</div></div></div>