Re: Using a display connection name fails (through NewtFactory)
Posted by Sven Gothel on Jun 10, 2013; 7:54pm
URL: https://forum.jogamp.org/Using-a-display-connection-name-fails-through-NewtFactory-tp4029333p4029369.html
On 06/10/2013 09:36 PM, neothemachine [via jogamp] wrote:
>> and start them:
>> jogl/make> bash scripts/tests-x64.sh
>
> I just built gluegen & jogl successfully and tried to run
> > bash scripts/tests-x32.sh from the jogl/make folder but it just says
> "build-dir ../build-x86 is not a directory".
>
> On http://jogamp.org/jogl/doc/HowToBuild.html it says that one should
> run "ant junit.run" which actually works.
>
> Can you explain that a bit more?ofc ..
- junit.run is the offical way to run _all_ unit tests.
- scripts/* are my private stash of 'convenient' build and test scripts.
- Note: Our builds environment is able to build multiple targets to their
respective build folder to simplify building/testing for different
OS and architectures.
- scripts/tests-x[32|64].sh
- run a single test w/ given properties to enable debug
- assume either build-x32 builds via scripts/make.jogl.all.linux-x86_64.sh, or
build-x32 via scripts/make.jogl.all.linux-x86.sh
- my build/test scripts utilize our ant build-time properties
- rootrel.build - to specify the build directory
- os.arch - to force a 32bit build on 64bit OS
See 'Note' above
- when using the scripts/* stuff, pls check the scripts themselves and
the locations/folder ..
- I for example use the x86_64 build scripts and have a symbolic link to 'build',
allowing eclipse workspace to pick it up.
build -> build-x86_64
~Sven
URL: https://forum.jogamp.org/Using-a-display-connection-name-fails-through-NewtFactory-tp4029333p4029369.html
On 06/10/2013 09:36 PM, neothemachine [via jogamp] wrote:
>> and start them:
>> jogl/make> bash scripts/tests-x64.sh
>
> I just built gluegen & jogl successfully and tried to run
> > bash scripts/tests-x32.sh from the jogl/make folder but it just says
> "build-dir ../build-x86 is not a directory".
>
> On http://jogamp.org/jogl/doc/HowToBuild.html it says that one should
> run "ant junit.run" which actually works.
>
> Can you explain that a bit more?
- junit.run is the offical way to run _all_ unit tests.
- scripts/* are my private stash of 'convenient' build and test scripts.
- Note: Our builds environment is able to build multiple targets to their
respective build folder to simplify building/testing for different
OS and architectures.
- scripts/tests-x[32|64].sh
- run a single test w/ given properties to enable debug
- assume either build-x32 builds via scripts/make.jogl.all.linux-x86_64.sh, or
build-x32 via scripts/make.jogl.all.linux-x86.sh
- my build/test scripts utilize our ant build-time properties
- rootrel.build - to specify the build directory
- os.arch - to force a 32bit build on 64bit OS
See 'Note' above
- when using the scripts/* stuff, pls check the scripts themselves and
the locations/folder ..
- I for example use the x86_64 build scripts and have a symbolic link to 'build',
allowing eclipse workspace to pick it up.
build -> build-x86_64
~Sven
signature.asc (911 bytes) | Free forum by Nabble | Edit this page |