Matthew Gregory wrote:
* a parameter in the build toolchain to allow to specify where the SDK will be
after a compile source build. This would allow to to compile source and then
move source somewhere else. I know source is not for production but for
validation purpose or to solve a tricky bug, we need debug message in prod
environment for example, so this may be improved either by allowing (not by
default) debug message in compile build (how to still get the correct file and
line number in errors ?) or by simplifying compile source SDK path problem.
I'm quite sure Thomas added support so you could modify macros from the
command line, you should be able to use this for what you want.
The way the source version is currently built burns relative paths to
all relevant libraries into the generated script. You can tweak the
"compile-source/root" config setting, to specify the target directory
for the index.html from which the app will eventually be loaded (and,
yes, you could do this via a macro, the value of which you supply with a
command-line option). Then all relative paths will be relative to *that*
target directory. But that requires that all libraries stay where they
are, *including* the app you are building. Just the index.html is in the
remote location.
Alternatively, the "library" config key allows you to specify a "uri"
sub-key. You would have to list all of the involved libraries including
the current app, and add "uri" keys to each entry. The "uri" key could
be a relative path from the remote index.html, or an absolute URI
starting with "http://...";.
I would be interested to learn if either of this works for JBB.
T.
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
