Re: gluegen - examples needed
Posted by
peterk on
Jul 23, 2014; 3:39am
URL: https://forum.jogamp.org/gluegen-examples-needed-tp4031123p4032639.html
Ok - looked in the GlueGenTask.java source for the ant task and saw:
gluegenCommandline.createArgument().setValue("-O" +
outputRootDir);
I assume this is an undocumented command line argument for what is
needed and will try it.
On 7/22/2014 9:27 PM, Wade Walker [via jogamp] wrote:
peterk wrote
If the directives in the config files
are overridable with gluegen command line arguments,
ie: the JavaOutputDir,and NativeOutputDir I'll do that.
If not if I include a build generated config file on the command line
will it specify those values for all config files following it on the
command line if they do not set these values themselves?
If so will the path specified for the output directory be interpreted
relative to the config file containing the directive, or to the config
file specifying the output to be generated?
If you look at the JOCL project source code (which is the one I'm most
familiar with, since I just had to work on this stuff recently),
jocl/make/build.xml shows how the gluegen tool is invoked with an
"output root directory", which should also be a command-line argument
to gluegen. The config files (like jocl/make/config/cl-common.cfg) use
JavaOutputDir and NativeOutputDir to specify output directories
relative to that root directory. So it should be entirely possible for
you to have a separate build directory and keep your source directory
read-only -- that's what JOCL does also.