Hm, I am still confused and I think we still have a problem here.
What we want to achieve is to be able to override the QOOXDOO_PATH macro
depending on the build environment.
I am running the trunk version of qooxdoo and the issue with ":" in the path
is indeed fixed.
However, the generate script still seems to rely on the path defined in
config.json:
C:\temp\qx\demo2>generate.py -m QOOXDOO_PATH:c:/work/qooxdoo_trunk
Cannot find real generator script under:
"C:\temp\qx\demo2\QOOXDOO_PATH_FROM_CONFIG.JSON\tool\bin\generator.py";
aborting
>From my config.json:
..
"let" :
{
"APPLICATION" : "demo2",
"QOOXDOO_PATH" : "QOOXDOO_PATH_FROM_CONFIG.JSON",
..
Am I missing something?
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/absolute-path-in-m-QOOXDOO-PATH-tp5788247p5791912.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
