Erik, I already tried manipulating the paths before they are fed to computeDependencyCalls, particularly I tried passing relative paths instead of absolute ones but that does not work either. One way or another the computeDependencyCalls() passes the path to PathUtil.makeAbsolute()and it gets corrupt.
If you look at the source code you will see that the entire com.google.javascript.jscomp.deps.PathUtil class uses hardcoded forward slash "/" as path separator in multiple functions and they work incorrect under Windows. I will look further to find a solution. Tigran. -----Original Message----- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Monday, April 08, 2013 4:37 PM To: dev@flex.apache.org Subject: Re: FalconJX: bugs in external dependencies (Google Closure Compiler), what to do? Tigran, Both Alex and I are on a Mac, so that is probably why it escaped notice until now :-) Also, the "publisher" side of the code is very much a work in progress, which deserves all the attention you can give it. I'll answer your other email some time tonight, jetlag permitting. On this one: might manipulation the path(s) before they are fed into the 'depswriter' - working from memory, might be missing the point - help avoid this low level problem? EdB On Mon, Apr 8, 2013 at 6:27 AM, Tigran Najaryan <tig...@gmail.com> wrote: > I debugged the problem that I reported earlier (generating incorrect > paths in deps.js) and looks like it is due to a bug in > com.google.javascript.jscomp.deps.PathUtil.isAbsolute. It is > implemented by simply checking that the path starts by a forward slash > which of course is incorrect under Windows. > > So what is the procedure when the bug is in an external dependency? It > is not as if it is a single call that can be avoided. > PathUtil.isAbsolute is called a few levels below in the call stack > from the > com.google.javascript.jscomp.deps.DepsGenerator.computeDependencyCalls > , which is supposed to compute and return the correct text for > dependencies file. > > I will debug this further but just wanted to understand if I should I > try to work around the external bug when I meet one or I need to try > something else? > > Tigran. > > P.S. Did anyone actually try running FalconJX on Windows or everybody > is developing on a Mac? > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
