Bug 390

Summary:	JUnit tests: rootrel.build is ignored / compiler target arch is ignored
Product:	[JogAmp] Gluegen	Reporter:	Sven Gothel <sgothel>
Component:	core	Assignee:	Sven Gothel <sgothel>
Status:	VERIFIED FIXED
Severity:	normal
Priority:	---
Version:	2
Hardware:	All
OS:	all
Type:	---	SCM Refs:	3a32650d4229f9b4ad1f527d9e30c24ddb69bb3f 9a1b43908b3bb1cd5dd5fadafb3b23d6e9a2cf46 7fe91321c0617e3035f1168784d799bcfe44f47a 6eeede0843f199e2f81291354c6e02e1a262f4da f06e190ef1b7c84433c5e3d9f7ce1e3899d4d7e9
Workaround:	---

Description Sven Gothel 2010-03-25 08:05:04 CET

The current junit tests use a fixed 'build' sub-path,
not the customizing 'rootrel.build' path.

More properties needs to be passed through (ant -> junit -> ant)
to comply with the current build system:
 * rootrel.build
 * os.arch
 * gluegen.user.compiler.file

However .. since even more properties may influence the build,
a more native solution with just plain 'ant' might be more desireable ..

Comment 1 Sven Gothel 2010-03-25 08:08:25 CET

Fixed as described.

However a more elaborated solution within pure 'ant' is desired!

Comment 2 Sven Gothel 2010-03-25 17:49:03 CET

    Adding 'plain' junit tests.
    Plain stands for the simple processing of:
        ant.junit.compile: gluegen -> java/c files, javac/cc, jar
        ant.junit.run:     junit batch run
    
    Avoiding 'black magic', ie kicking off gluegen and ant-compilation
    from within the junit tests.
    
    Same methodology as the JOGL junit tests,
    junit test sources are under 'src/junit'
    
    This way, the migration to other platform tests might be easier,
    as well as the we don't need to pass through ant properties (ant - junit - ant),
    see 3a32650d4229f9b4ad1f527d9e30c24ddb69bb3f.

Comment 3 Sven Gothel 2010-03-25 18:48:24 CET

- use gluegen.root
- use build_t as a unique property for build-junit.xml
  (build is used by build.xml)
- invoke junit.run on test