Yeah, I stepped through the code till my feet hurt ;-) That didn't give me anything, as the errors are thrown when the compilation units are still being gathered, so no actual compilation is done.
A search of the entire SDK gives these references to 'MiniDebugTaget': /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/spark-manifest.xml:295 <component id="MiniDebugTarget" class="mx.logging.targets.MiniDebugTarget" lookupOnly="true"/> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/framework/src/mx/logging/Log.as:57 * There are two targets provided: <code>MiniDebugTarget</code> and /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/spark/manifest.xml:295 <component id="MiniDebugTarget" class="mx.logging.targets.MiniDebugTarget" lookupOnly="true"/> Not sure what the 'lookupOnly="true"' means ... does that attribute allow the old compiler to ignore the lack of a 'MiniDebugTarget.as' file anywhere in the SDK? EdB On Mon, Nov 3, 2014 at 5:06 PM, Alex Harui <aha...@adobe.com> wrote: > Maybe you’ve already tried this, but what I typically do when getting an > unexpected/undesirable error in Falcon/FalconJX is put a breakpoint on the > constructor of the XXXProblem class. > > When the constructor gets hit, up the call stack is hopefully the node > being processed. In the variables window if you examine the node, you > should see the line number and the file as well. For example: > > ClassNode(ClassID) "ProductFilter" 21:0 loc: 1025-1935 abs: 1025-1935 > /Users/aharui/Flex Demos/FlexJSStore/src/samples/flexstore/ProductFilter.as > > means line #21 in ProductFilter.as > > > -Alex > > On 11/2/14, 11:23 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > > >It's a 'NoSourceForClassInNamespaceProblem', and the only places that is > >'thrown' is in SWCTarget (Falcon) and FlexJSSWCTarget (FalconJX). It is > >referenced in both the 'validateIncludeNamespaceEntries' and > >'getCompilationUnitsFromClassNames' methods. > > > >It seems related to the actual compilation of the source, not the > >'cross-compilation/parsing' of the AST to JS. > > > >If you look at the "FlexSDKToJS" script I committed, you can see the > >actual > >command line arguments I use to put the SDK through FalconJX. Maybe that > >gives a clue? > > > >EdB > > > > > > > >On Mon, Nov 3, 2014 at 6:52 AM, Alex Harui <aha...@adobe.com> wrote: > > > >> Interesting. Have you found where the “could not find source” is > >>output? > >> If you break on that, you can usually find out which source file is > >>being > >> compiled and look at the source and try to figure out why. > >> > >> It could just be unused import statements in those source files. > >>FalconJX > >> I think relies on accurate imports to chase dependencies. > >> > >> -Alex > >> > >> On 11/2/14, 9:10 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > >> > >> >If I leave out "-external-library-path=fds.swc", I get: > >> > > >> ><errors> > >> > > >> >Could not find source for class mx.data.mxml.DataService in namespace > >> >library://ns.adobe.com/flex/spark. > >> > > >> >Could not find source for class > >>mx.messaging.channels.SecureRTMPChannel in > >> >namespace library://ns.adobe.com/flex/spark. > >> > > >> >Could not find source for class mx.messaging.channels.RTMPChannel in > >> >namespace library://ns.adobe.com/flex/spark. > >> > > >> ></errors> > >> >And if I leave out "-source-path=mx.logging.targets.MiniDebugTarget", I > >> >get: > >> > > >> ></errors> > >> > > >> >Could not find source for class mx.logging.targets.MiniDebugTarget in > >> >namespace library://ns.adobe.com/flex/spark. > >> > > >> ></errors> > >> > > >> >Thanks, > >> > > >> >EdB > >> > > >> > > >> > > >> >On Sun, Nov 2, 2014 at 6:38 AM, Alex Harui <aha...@adobe.com> wrote: > >> > > >> >> What errors do you get? > >> >> > >> >> On 10/31/14, 11:47 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > >> >> > >> >> >Hi, > >> >> > > >> >> >When compiling the Flex SDK to JS with FalconJX (not Falcon), I get > >> >>errors > >> >> >if I don't include these files: > >> >> > > >> >> >-source-path=mx.logging.targets.MiniDebugTarget > >> >> > > >> >> >-external-library-path=fds.swc > >> >> > > >> >> >At first I could not find these files at all (they are not in the > >> >>repo), > >> >> >but finally Google found them for me: the 'MiniDebugTarget.as' was > >>last > >> >> >seen as part of the Adobe Flex 3.6 SDK and 'fds.swc' is/was part of > >> >> >'something something LiveCycle' and can only be found in some guy's > >> >>Github > >> >> >repo. > >> >> > > >> >> >2 questions: how do I get rid of these dependencies, it seems the > >>SDK > >> >>to > >> >> >SWC compilers don't need them? And: if I can't get rid of them, what > >> >>would > >> >> >be the best way to find and include them? > >> >> > > >> >> >EdB > >> >> > > >> >> > > >> >> > > >> >> >-- > >> >> >Ix Multimedia Software > >> >> > > >> >> >Jan Luykenstraat 27 > >> >> >3521 VB Utrecht > >> >> > > >> >> >T. 06-51952295 > >> >> >I. www.ixsoftware.nl > >> >> > >> >> > >> > > >> > > >> >-- > >> >Ix Multimedia Software > >> > > >> >Jan Luykenstraat 27 > >> >3521 VB Utrecht > >> > > >> >T. 06-51952295 > >> >I. www.ixsoftware.nl > >> > >> > > > > > >-- > >Ix Multimedia Software > > > >Jan Luykenstraat 27 > >3521 VB Utrecht > > > >T. 06-51952295 > >I. www.ixsoftware.nl > > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
