I had already done pretty close to this (using outdated files, so I just
updated it).
I’m running into environment variable issues again and I tried to set up a
env.properties file to set them, but that’s not working. (I’m not exactly sure
what the variables are supposed to point to)
Here’s the file I created:
env.AIR_HOME=/Users/harbs/Documents/ApacheFlex/frameworks/AIRSDK_Compiler
env.FLASHPLAYER_DEBUGGER=/Users/harbs/Documents/ApacheFlex/frameworks/Flash
Player Debugger.app/Contents/MacOS/Flash Player Debugger
env.FALCON_HOME=/Users/harbs/Documents/ApacheFlex/flex-falcon/compiler
env.FALCONJX_HOME=/Users/harbs/Documents/ApacheFlex/flex-falcon/compiler.jx
and I get the following errors:
compile-asjs:
[echo] Cross-compiling XML-0.6.0.swc
[echo] FALCONJX_HOME: ${env.FALCONJX_HOME}
[java] Error: Unable to access jarfile
/Users/harbs/Documents/ApacheFlex/flex-asjs/frameworks/projects/XML/${env.FALCONJX_HOME}/lib/compc.jar
[java] Java Result: 1
compile-extern-swc:
[echo] Compiling target/externs/XML-0.6.0.swc
[echo] FLEX_HOME: /Users/harbs/Documents/ApacheFlex/flex-asjs
[echo] FALCON_HOME: ${env.FALCON_HOME}
How do we simplify setting environment variables? What I’ve been doing is
writing shell scripts for every custom build I do, but that’s ridiculous, and
it creates a barrier for others wanting to get involved.
On Feb 11, 2016, at 5:59 PM, Alex Harui <aha...@adobe.com> wrote:
> IIRC, you are trying to get the build to work in a new XML folder?
>
> In theory, you can copy any build.xml from, say Binding into the root of
> XML. Open it and search for Binding and replace with XML.
>
> Next, copy the src/main/resources folder from Binding. Open
> compile-config.xml and search and replace Binding.
>
> Open compile-asjs-config.xml and do the same.
>
> If you don't have a src/main/flex/XMLClasses.as file, create one and list
> the files you want to compile. If you don't want a particular class in
> the AS version of the SWC, put it in a COMPILE::AS3 block.
>
> Open basic-manifest.xml and comment everything out. This is the list of
> components that go in MXML, but I think you are emulating classes that are
> already in the fx: namespace so you shouldn't need anything.
>
> Then running "ant" from XML should "do the right thing".
>
> To integrate into the main build, open frameworks/build.xml, search for
> Binding and clone the patterns you see.
>
> HTH,
> -Alex
>
> On 2/11/16, 1:25 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>
>> OK. I merged and copied the new folder structure. Unfortunately I have no
>> idea how to set up the compilation. I just copied the folder structure
>> like a monkey, but I have no idea how it’s supposed to work.
>>
>> Can someone help me set up the scripts so it can actually compile
>> something? Once I understand how the compilation is supposed to work, I
>> can continue with this.
>>
>> Harbs
>>
>> On Feb 11, 2016, at 10:56 AM, Harbs <harbs.li...@gmail.com> wrote:
>>
>>> OK. I’m up to #2. I know of a number of problems/holes in the
>>> implementation as it stands and there’s probably a lot of problems I’m
>>> not aware of, but I’m going to try to get to the point where this
>>> compiles and actually does something to make the problems more visible.
>>>
>>> Maybe some other folks can even help at that point… ;-)
>>>
>>> On Feb 8, 2016, at 11:00 AM, Harbs <harbs.li...@gmail.com> wrote:
>>>
>>>> So here’s my current plan:
>>>> 1. Finish up the methods (minus filtering) in the next day or two.
>>>> 2. Sync up XML with the current FlexJS folder structure and get rid of
>>>> some junk (like all the JXON classes).
>>>> 3. Get this all to compile.
>>>> 4. Figure out the whole filtering issue.
>>>> 5. Create test cases.
>>>
>>
>
