Closed GoogleCodeExporter closed 9 years ago
...found this solution:
$(DIR)/../../../src/main/native/myHeader.h
or:
$(DIR)/../native/myHeader.h
(sorry ;-) )
do not know if the proposal still makes sense now. feel free to close it.
Original comment by robin.vobruba@gmail.com
on 13 Sep 2010 at 10:10
Hello Robin,
Thanks for your proposal and kind feedback :-)
While the workaround you found should be technically enough (I'm using it in
JavaCL and Mono4Java, for instance), I guess it won't hurt if I also expose
some Maven-specific variables as JNAerator file variables to avoid having to
resort to ../.. sequences (the $(VAR) syntax already gives access to
environment variables and Java properties, but not the maven properties yet).
If you see other variables than project.basedir, feel free to list them here so
I take them into account when I find some time for this enhancement.
Cheers
--
Olivier
Original comment by olivier.chafik@gmail.com
on 13 Sep 2010 at 1:04
:-)
yeah, found it in the docu and your examples just after posting. ;-)
had a look at the other default maven properties, and none really seemed useful
here, except maybe:
* ${project.build.directory} results in the path to your "target" dir
in case someone is generating the headers to parse... though that would be
strange.
Original comment by robin.vobruba@gmail.com
on 13 Sep 2010 at 8:54
Hi,
This issue moved to Github :
https://github.com/ochafik/nativelibs4java/issues/177
Thanks for not updating this page anymore and adding further comments on Github.
Cheers
--
zOlive
Original comment by olivier.chafik@gmail.com
on 1 Sep 2011 at 7:28
Original issue reported on code.google.com by
robin.vobruba@gmail.com
on 13 Sep 2010 at 10:03