Hey Nicolas, Okay, I figured out the bug, and I think I have it fixed. No need to share your code or compiler output anymore! Once the next nightly build finishes, you should be able to download it to get the fix.
It turned out to be a case sensitivity issue. I was able to reproduce the issue when I typed the Windows drive letter in uppercase when I set the output compiler option to an absolute path. The compiler seemed to be expecting lowercase instead when it was doing some equality checks. Slashes were actually not a problem. It looks like Java is correctly switching everything to backslash on Windows If you don't want to update to a nightly build, you should be able to workaround the issue instead. Play around with the absolute path that you pass to the output compiler option. It could be as simple as changing the case of the drive letter (if it's uppercase, try lowercase... or if it's lowercase, try uppercase). If that doesn't work, you might also need to check that you're using the correct case of any directory names in the path too. - Josh On 2017-09-28 15:04, "Idylog - Nicolas Granon" <ngra...@idylog.com> wrote: > Hi Josh, > > Thank you for your answer. > > The "web server" is installed locally. > In the compiler arguments, it is just a directory path outside the workspace > with an absolute path (c:/etc.). > And yes, the drive is the same. > > Is it possible that forward slashes or backward slashes make a difference ? > (I have the habit of using forward slashes, even on Windows, if it is > accepted) > > I have no problem sharing the compiler output but it's midnight now here ! I > will do this tomorrow if you don't mind... > > The mxml (sole) file content is quite simple and I tried to stick to your > demo at FlexCon. > > Should I sent the output file to the mailing list or to another address ? > (no problem for me for sending public. It's only a basic test !!) > > Thanks again, > > Nicolas Granon > > > > > > -----Message d'origine----- > > De : Josh Tynjala [mailto:joshtynj...@apache.org] > > Envoyé : jeudi 28 septembre 2017 23:06 > > à: users@flex.apache.org > > Objet : Re: [FlexJS] Compiler outputs (nearly) empty map file > > > > Hi Nicolas, > > > > I just gave it a try on my machine with FlexJS 0.8, and source map file > > contained the correct information for the functions in the <fx:Script> > > tag when I set the source-map option to true and provided a custom > > output path. I tried both absolute and relative output paths, and the > > contents of the .map file were correct in all cases. The "sources" > > field of the .map file even had different paths back to the .mxml file, > > depending on where it had been output. I'm on macOS, but I'll make sure > > to test on Windows too. > > > > I noticed that you mentioned sending the output to a web server. Is > > this on the same drive that your workspace is saved, or are you > > outputting to another drive or somewhere else that might be > > unconventional? > > > > Can you share the complete output from the compiler? > > > > Can you also share the contents of myproject03.mxml and asconfig.json? > > > > These might provide some clues that will help me figure out how to > > reproduce the issue. Thanks! > > > > Note: As others have mentioned, the .js.map file name issue is indeed > > fixed. If you use a nightly build, the file name properly ends with > > .mxml.map instead of .js.map. However, it's worth noting that it should > > work without any file name changes if you debug in Visual Studio Code > > using the Chrome browser. At least, that was the case the last time > > that I tried. > > > > - Josh > > > > On 2017-09-27 02:24, "Idylog - Nicolas Granon" <ngra...@idylog.com> > > wrote: > > > We are trying to use FlexJS 0.8 with a Visual Studio Code (VSCode) > > > setup (nextgen actionscript extension). > > > > > > Everything works fine. However, when we use the -source-map option of > > > the compiler (in the asconfig.json) a source map file is created > > > ({project > > > name}.js.map) with the correct keys, but no values ! > > > > > > Here is a copy of the content of the {project name}.js.map : > > > > > > { > > > "version":3, > > > "file":"myproject03.js", > > > "lineCount":1, > > > "mappings":";", > > > "sources":[], > > > "names":[] > > > } > > > > > > I have understood that the map generated from MXML files should be > > > named .mxml.map. But this is not our concern (we can rename the file > > > until this small bug is fixed). > > > > > > The problem is of course that the file is "empty". > > > > > > The project consists of a single mxml file (with a button, a label > > and > > > a listener displaying an Alert, nothing very complicated !). > > > The listener is inside a script tag, of course, not inlined. > > > We have the latest version of VSCode (august 2017), the latest > > version > > > of NextGenAS extension (0.6.0). > > > The only specific (?) setting is that we use the --output argument > > > since we want to sent the compiled output to our web server (the > > > output dir is one level BELOW the web root but of course the output > > > dir is specified as an absolute windows path, not as a URL). And also > > > we output JS only (--target JSFlex). > > > The generated output in bin-debug runs fine... > > > > > > What did we miss ? > > > > > > Many thanks > > > > > > Nicolas > > > > > > > >
