RE: Building the SDK from git
Yep, I guess it is not the same doing a check out from windows (whatever the tool) and from Cygwin. -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : jeudi 26 septembre 2013 19:29 À : dev@flex.apache.org Objet : RE: Building the SDK from git Yeah I'm Windows with TortoiseGit, didn't have to change anything out of the box for that. It's setup to translate into Windows cr/lf and then back again automatically. -Original Message- From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] It depends the OS, on Windows it is recommended to set it to "true", "input" on others but if you're on windows but use Cygwin, it has to be set to "input".
RE: Building the SDK from git
Yeah I'm Windows with TortoiseGit, didn't have to change anything out of the box for that. It's setup to translate into Windows cr/lf and then back again automatically. -Original Message- From: Frédéric THOMAS [mailto:webdoubl...@hotmail.com] It depends the OS, on Windows it is recommended to set it to "true", "input" on others but if you're on windows but use Cygwin, it has to be set to "input".
RE: Building the SDK from git
At least it what I deducted because it happened to me I checkout the dev branch with autocrlf=true and wasn't able to build from ant on Cygwin, the build scripts wasn't read correctly, changing it by autocrlf=input, checking out again made it running correctly. -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : jeudi 26 septembre 2013 19:24 À : dev@flex.apache.org Objet : RE: Building the SDK from git It depends the OS, on Windows it is recommended to set it to "true", "input" on others but if you're on windows but use Cygwin, it has to be set to "input". -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : jeudi 26 septembre 2013 19:20 À : dev@flex.apache.org Objet : RE: Building the SDK from git Just a small note. The git property changes are independent of the sdk specifically and more geared toward which git client you use on how to change the properties. -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] 6) Fred told me I should set " core.autocrlf" to "input" to avoid issues when committing from Windows. => I think this should be set per-repository in the .gitattributes of flex-sdk and flex-tlf, so that everyone has the same settings, and we don't have to bother about that anymore.
RE: Building the SDK from git
It depends the OS, on Windows it is recommended to set it to "true", "input" on others but if you're on windows but use Cygwin, it has to be set to "input". -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : jeudi 26 septembre 2013 19:20 À : dev@flex.apache.org Objet : RE: Building the SDK from git Just a small note. The git property changes are independent of the sdk specifically and more geared toward which git client you use on how to change the properties. -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] 6) Fred told me I should set " core.autocrlf" to "input" to avoid issues when committing from Windows. => I think this should be set per-repository in the .gitattributes of flex-sdk and flex-tlf, so that everyone has the same settings, and we don't have to bother about that anymore.
RE: Building the SDK from git
Just a small note. The git property changes are independent of the sdk specifically and more geared toward which git client you use on how to change the properties. -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] 6) Fred told me I should set " core.autocrlf" to "input" to avoid issues when committing from Windows. => I think this should be set per-repository in the .gitattributes of flex-sdk and flex-tlf, so that everyone has the same settings, and we don't have to bother about that anymore.
RE: Building the SDK from git
-Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 18:58 À : dev@flex.apache.org Objet : RE: Building the SDK from git Hi, This is my (uncensored :-) feedback following the SDK build. 1) Doc inconsistency: There are 3 differents docs explaining how to build the SDK: - WIKI: https://cwiki.apache.org/confluence/display/FLEX/1.2+Setting+up+Manually - WEB: http://flex.apache.org/dev-sourcecode.html - README file in sdk root. Which contain the potentially inconsistent information: a) README says JAVA 1.6 minimum is required , whereas WIKI only states "download java". I was using JDK 1.5 and got into an issue when building the "modules" (target 1.6 not valid). => I think the wiki shoul also mention 1.6 minimum requirement b) git commands to retrieve the repos: - README says git clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git sdk - WEB says same as README - WIKI says git clone [https://git-wip-us.apache.org/repos/asf/flex-sdk.git] flex-sdk True, it is inconsistent but both work. Note: actually, maybe 3 sources of information on how to build the SDK are just too much. Maybe only the WIKI should be kept, and the README just provide a link to the wiki. That would make maintenance easier. 2) When launching the build for the first time, it fails because the "modules" (FlexTasks, mxmlc, etc..) are not built yet. => either mention in the doc that modules needs to be built before hand => or better, add a dependency in the main build so that it's done automatically , if not present. ant thirdparty-downloads should be enough to run once only, you can then run the other targets, I never had to run explicitly any builds from the modules. 3) missing values: TLF_HOME is missing from env-template.properties True but it is not mandatory ant still mentioned in the readme 4) build.properties not up to date => fixed 5) .actionScriptProperties and .flexLibProperties are missing from .gitignore => controversial. Some of those files are in the repo already, so, it can be added to the main .gitignore only if we add .gitignore files in the folders where they stand, why not. 6) Fred told me I should set " core.autocrlf" to "input" to avoid issues when committing from Windows. => I think this should be set per-repository in the .gitattributes of flex-sdk and flex-tlf, so that everyone has the same settings, and we don't have to bother about that anymore. The default for windows seems to be "true" and "input" for other OSes but because I run the Ant tasks from Cygwin, I had to set it to "input" for not having build issues. 7) Fred says I need to run "ant other.locales" to avoid trouble in French env. This is not mentioned anywhere in the doc. => Add to the WIKI. Or you can run ant -Dlocale=fr_FR only to go faster and it is mention in the readme. Regards, Maurice -Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 26 septembre 2013 18:32 À : dev@flex.apache.org Objet : Re: Building the SDK from git On 9/26/13 9:12 AM, "Maurice Amsellem" wrote: >BUILD SUCCESSFUL! > >YEEHAA! > >Do you me to recap the few issues I have faced as a "newbie"? Sure. I think you'll be getting write access soon, so then you'll be able to update the README yourself. -Alex
RE: Building the SDK from git
Hi, This is my (uncensored :-) feedback following the SDK build. 1) Doc inconsistency: There are 3 differents docs explaining how to build the SDK: - WIKI: https://cwiki.apache.org/confluence/display/FLEX/1.2+Setting+up+Manually - WEB: http://flex.apache.org/dev-sourcecode.html - README file in sdk root. Which contain the potentially inconsistent information: a) README says JAVA 1.6 minimum is required , whereas WIKI only states "download java". I was using JDK 1.5 and got into an issue when building the "modules" (target 1.6 not valid). => I think the wiki shoul also mention 1.6 minimum requirement b) git commands to retrieve the repos: - README says git clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git sdk - WEB says same as README - WIKI says git clone [https://git-wip-us.apache.org/repos/asf/flex-sdk.git] flex-sdk Note: actually, maybe 3 sources of information on how to build the SDK are just too much. Maybe only the WIKI should be kept, and the README just provide a link to the wiki. That would make maintenance easier. 2) When launching the build for the first time, it fails because the "modules" (FlexTasks, mxmlc, etc..) are not built yet. => either mention in the doc that modules needs to be built before hand => or better, add a dependency in the main build so that it's done automatically , if not present. 3) missing values: TLF_HOME is missing from env-template.properties 4) build.properties not up to date => fixed 5) .actionScriptProperties and .flexLibProperties are missing from .gitignore => controversial. 6) Fred told me I should set " core.autocrlf" to "input" to avoid issues when committing from Windows. => I think this should be set per-repository in the .gitattributes of flex-sdk and flex-tlf, so that everyone has the same settings, and we don't have to bother about that anymore. 7) Fred says I need to run "ant other.locales" to avoid trouble in French env. This is not mentioned anywhere in the doc. => Add to the WIKI. Regards, Maurice -Message d'origine- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 26 septembre 2013 18:32 À : dev@flex.apache.org Objet : Re: Building the SDK from git On 9/26/13 9:12 AM, "Maurice Amsellem" wrote: >BUILD SUCCESSFUL! > >YEEHAA! > >Do you me to recap the few issues I have faced as a "newbie"? Sure. I think you'll be getting write access soon, so then you'll be able to update the README yourself. -Alex
Re: Building the SDK from git
River Song would say: "Spoilers!" The bane of time travellers all over the universe... ;-) EdB On Thu, Sep 26, 2013 at 6:32 PM, Alex Harui wrote: > > > On 9/26/13 9:12 AM, "Maurice Amsellem" wrote: > >>BUILD SUCCESSFUL! >> >>YEEHAA! >> >>Do you me to recap the few issues I have faced as a "newbie"? > Sure. I think you'll be getting write access soon, so then you'll be able > to update the README yourself. > > -Alex > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Building the SDK from git
On 9/26/13 9:12 AM, "Maurice Amsellem" wrote: >BUILD SUCCESSFUL! > >YEEHAA! > >Do you me to recap the few issues I have faced as a "newbie"? Sure. I think you'll be getting write access soon, so then you'll be able to update the README yourself. -Alex
RE: Building the SDK from git
BUILD SUCCESSFUL! YEEHAA! Do you me to recap the few issues I have faced as a "newbie"? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 17:42 À : dev@flex.apache.org Objet : RE: Building the SDK from git Thanks, that's really helpful. I understand I launch the general build.xml the first time only, and then only need to run the build.xml for the project I am working on (eg. experimental/build.xml) which will compile rather quickly. Is that correct ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 26 septembre 2013 17:04 À : dev@flex.apache.org Objet : Re: Building the SDK from git Hi, > Please can you share how you proceed to compile when you make even small > changes to the code and would like to test them. > Are you using an IDE at all ? I normally use Flash Builder to edit files (but sometimes vi from the command line) and I normally compile using ant from the command line. I have the entire SDK as a single general project, that way it works nicely when debugging, but there's probably other ways of setting it up. Ant can be run from within Flash Builder, right right click on a build.xml file and select Run As then "Ant build" (which will do an ant main), if you select "Ant build..." you can specify which target to run. I'd assume other IDE's have the same feature. Once you have an SDK set up you can compile each project in framework/projects as you make changes, they compile reasonable quickly (under a min for each one). Just be careful is using Flash Builder this was as sometime (not often) it can cache the pervious versions, if so just swap the project SDK to another then back again and that seem to clear the cache. Thanks, Justin
RE: Building the SDK from git
Thanks, that's really helpful. I understand I launch the general build.xml the first time only, and then only need to run the build.xml for the project I am working on (eg. experimental/build.xml) which will compile rather quickly. Is that correct ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 26 septembre 2013 17:04 À : dev@flex.apache.org Objet : Re: Building the SDK from git Hi, > Please can you share how you proceed to compile when you make even small > changes to the code and would like to test them. > Are you using an IDE at all ? I normally use Flash Builder to edit files (but sometimes vi from the command line) and I normally compile using ant from the command line. I have the entire SDK as a single general project, that way it works nicely when debugging, but there's probably other ways of setting it up. Ant can be run from within Flash Builder, right right click on a build.xml file and select Run As then "Ant build" (which will do an ant main), if you select "Ant build..." you can specify which target to run. I'd assume other IDE's have the same feature. Once you have an SDK set up you can compile each project in framework/projects as you make changes, they compile reasonable quickly (under a min for each one). Just be careful is using Flash Builder this was as sometime (not often) it can cache the pervious versions, if so just swap the project SDK to another then back again and that seem to clear the cache. Thanks, Justin
Re: Building the SDK from git
The Mustella test suite is run on the VM against FP 11.1, 11.7, 11.8 and 11.9; each at least once every two days. These versions appear all equal in the eyes of the SDK. EdB On Thu, Sep 26, 2013 at 5:06 PM, Justin Mclean wrote: > Hi, > >> However playerglobal.version is still 11.1. Does this mean I should compile >> agains FP 11.1? > You can compile against any version of the Flash Player from 10.2 onwards, we > try and keep it backwards compatible. People who use AIR generally want the > latest, people who use Flash Player may not be able to use the latest so 11.1 > is a safe bet. Version Adobe Flex 4.6 was tested/worked with so I tend to > default to that most of the time. > > You'll be fine with 11.8 or 11.1 - up to you. > > Thank, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Building the SDK from git
Hi, > However playerglobal.version is still 11.1. Does this mean I should compile > agains FP 11.1? You can compile against any version of the Flash Player from 10.2 onwards, we try and keep it backwards compatible. People who use AIR generally want the latest, people who use Flash Player may not be able to use the latest so 11.1 is a safe bet. Version Adobe Flex 4.6 was tested/worked with so I tend to default to that most of the time. You'll be fine with 11.8 or 11.1 - up to you. Thank, Justin
Re: Building the SDK from git
Hi, > Please can you share how you proceed to compile when you make even small > changes to the code and would like to test them. > Are you using an IDE at all ? I normally use Flash Builder to edit files (but sometimes vi from the command line) and I normally compile using ant from the command line. I have the entire SDK as a single general project, that way it works nicely when debugging, but there's probably other ways of setting it up. Ant can be run from within Flash Builder, right right click on a build.xml file and select Run As then "Ant build" (which will do an ant main), if you select "Ant build..." you can specify which target to run. I'd assume other IDE's have the same feature. Once you have an SDK set up you can compile each project in framework/projects as you make changes, they compile reasonable quickly (under a min for each one). Just be careful is using Flash Builder this was as sometime (not often) it can cache the pervious versions, if so just swap the project SDK to another then back again and that seem to clear the cache. Thanks, Justin
RE: Building the SDK from git
Justin, I noticed you updated air.version and release.version in build.properties. However playerglobal.version is still 11.1. Does this mean I should compile agains FP 11.1? On the other hand, the page https://cwiki.apache.org/confluence/display/FLEX/1.2+Setting+up+Manually says we should be using 11.8. Which one is correct? Or maybe it does not matter... Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 26 septembre 2013 15:12 À : dev@flex.apache.org Objet : Re: Building the SDK from git Hi, With TLF environment variables work fine. On OSX I have the following: TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/ PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex/in/player/11.1/mac/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 ANT_HOME=/usr/share/ant My flex home is: /Users/justinmclean/Documents/ApacheFlexDevelopGit Not all of these are required to be set to build the SDK, but are required to make a release and/or run the mustella tests. You're correct about the build.properties files I've updated the values in that and checked into develop. Thanks, Justin
RE: Building the SDK from git
Hi, My config is the following: - I have created a project in FB to map projects/experimental => added .actionScriptProps and .flexLibProps - Added both entries to .gitignore, to make sure they will not end up if any commit " given ant is the preferred build method." Please can you share how you proceed to compile when you make even small changes to the code and would like to test them. Are you using an IDE at all ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 26 septembre 2013 16:32 À : dev@flex.apache.org Objet : Re: Building the SDK from git Hi, > Yes, I think that is the idea... I think "we" somehow all ended up > with it in our local ignores It's not in mine and I've not seen any issues, but they probably shouldn't be in there in the first place, given ant is the preferred build method. Thanks, Justin
Re: Building the SDK from git
Hi, > Yes, I think that is the idea... I think "we" somehow all ended up > with it in our local ignores It's not in mine and I've not seen any issues, but they probably shouldn't be in there in the first place, given ant is the preferred build method. Thanks, Justin
Re: Building the SDK from git
Hi, > So maybe they should be included in the .gitignore (along with .project, > etc.) ? -1 to that. Anything that is actually in version control should not be in .gitignore, this has caused far too many issues in the past, including breaking a release candidate. IMO if something in version control needs to be added to .gitignore it shouldn't be in version control in the first place. Justin
RE: Building the SDK from git
Yes, I have tried to keep a "journal" of what I do and the issues I am facing. I will do it with that in mind from now on. (ie updating the resources at the end) Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : jeudi 26 septembre 2013 15:56 À : dev@flex.apache.org Objet : Re: Building the SDK from git Yes, I think that is the idea... I think "we" somehow all ended up with it in our local ignores, a legacy from the rather messy transition from SVN. Also, you raise a couple of good issues with the README and other docs. Would you mind keeping notes so once you're up and running we (i.e. you ;-)) can update those resources? Thanks! EdB On Thu, Sep 26, 2013 at 3:50 PM, Maurice Amsellem wrote: > Understood. > > So maybe they should be included in the .gitignore (along with .project, > etc.) ? > > Maurice > > -Message d'origine- > De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : jeudi 26 > septembre 2013 15:45 À : dev@flex.apache.org Objet : Re: Building the > SDK from git > > On purpose, we don't want IDE specific configuration files in git. > > EdB > > > > On Thu, Sep 26, 2013 at 3:36 PM, Maurice Amsellem > wrote: >> Also, I noticed .actionScriptProperties and .flexLibProperties are >> missing from framework/projects/experimental >> >> Not committed or is it on purpose ? >> >> Maurice >> >> >> -Message d'origine----- >> De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi >> 26 septembre 2013 15:12 À : dev@flex.apache.org Objet : Re: Building >> the SDK from git >> >> Hi, >> >> With TLF environment variables work fine. >> >> On OSX I have the following: >> TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ >> AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/ >> PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ >> FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe Flash >> Builder 4.6/Apache Flex/in/player/11.1/mac/Flash Player >> Debugger.app/Contents/MacOS/Flash Player Debugger >> PIXELBENDER_HOME=/Applications/Utilities/Adobe >> Utilities-CS5.localized/Pixel Bender Toolkit 2/ >> ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager >> CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension >> Manager CS5 ANT_HOME=/usr/share/ant >> >> My flex home is: >> /Users/justinmclean/Documents/ApacheFlexDevelopGit >> >> Not all of these are required to be set to build the SDK, but are required >> to make a release and/or run the mustella tests. >> >> You're correct about the build.properties files I've updated the values in >> that and checked into develop. >> >> Thanks, >> Justin > > > > -- > 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
Re: Building the SDK from git
Yes, I think that is the idea... I think "we" somehow all ended up with it in our local ignores, a legacy from the rather messy transition from SVN. Also, you raise a couple of good issues with the README and other docs. Would you mind keeping notes so once you're up and running we (i.e. you ;-)) can update those resources? Thanks! EdB On Thu, Sep 26, 2013 at 3:50 PM, Maurice Amsellem wrote: > Understood. > > So maybe they should be included in the .gitignore (along with .project, > etc.) ? > > Maurice > > -Message d'origine- > De : Erik de Bruin [mailto:e...@ixsoftware.nl] > Envoyé : jeudi 26 septembre 2013 15:45 > À : dev@flex.apache.org > Objet : Re: Building the SDK from git > > On purpose, we don't want IDE specific configuration files in git. > > EdB > > > > On Thu, Sep 26, 2013 at 3:36 PM, Maurice Amsellem > wrote: >> Also, I noticed .actionScriptProperties and .flexLibProperties are >> missing from framework/projects/experimental >> >> Not committed or is it on purpose ? >> >> Maurice >> >> >> -Message d'origine----- >> De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 26 >> septembre 2013 15:12 À : dev@flex.apache.org Objet : Re: Building the >> SDK from git >> >> Hi, >> >> With TLF environment variables work fine. >> >> On OSX I have the following: >> TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ >> AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/ >> PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ >> FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe Flash Builder >> 4.6/Apache Flex/in/player/11.1/mac/Flash Player >> Debugger.app/Contents/MacOS/Flash Player Debugger >> PIXELBENDER_HOME=/Applications/Utilities/Adobe >> Utilities-CS5.localized/Pixel Bender Toolkit 2/ >> ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager >> CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension >> Manager CS5 ANT_HOME=/usr/share/ant >> >> My flex home is: >> /Users/justinmclean/Documents/ApacheFlexDevelopGit >> >> Not all of these are required to be set to build the SDK, but are required >> to make a release and/or run the mustella tests. >> >> You're correct about the build.properties files I've updated the values in >> that and checked into develop. >> >> Thanks, >> Justin > > > > -- > 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
RE: Building the SDK from git
Understood. So maybe they should be included in the .gitignore (along with .project, etc.) ? Maurice -Message d'origine- De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : jeudi 26 septembre 2013 15:45 À : dev@flex.apache.org Objet : Re: Building the SDK from git On purpose, we don't want IDE specific configuration files in git. EdB On Thu, Sep 26, 2013 at 3:36 PM, Maurice Amsellem wrote: > Also, I noticed .actionScriptProperties and .flexLibProperties are > missing from framework/projects/experimental > > Not committed or is it on purpose ? > > Maurice > > > -Message d'origine- > De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 26 > septembre 2013 15:12 À : dev@flex.apache.org Objet : Re: Building the > SDK from git > > Hi, > > With TLF environment variables work fine. > > On OSX I have the following: > TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ > AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/ > PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ > FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe Flash Builder > 4.6/Apache Flex/in/player/11.1/mac/Flash Player > Debugger.app/Contents/MacOS/Flash Player Debugger > PIXELBENDER_HOME=/Applications/Utilities/Adobe > Utilities-CS5.localized/Pixel Bender Toolkit 2/ > ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager > CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension > Manager CS5 ANT_HOME=/usr/share/ant > > My flex home is: > /Users/justinmclean/Documents/ApacheFlexDevelopGit > > Not all of these are required to be set to build the SDK, but are required to > make a release and/or run the mustella tests. > > You're correct about the build.properties files I've updated the values in > that and checked into develop. > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: Building the SDK from git
On purpose, we don't want IDE specific configuration files in git. EdB On Thu, Sep 26, 2013 at 3:36 PM, Maurice Amsellem wrote: > Also, I noticed .actionScriptProperties and .flexLibProperties are missing > from framework/projects/experimental > > Not committed or is it on purpose ? > > Maurice > > > -Message d'origine- > De : Justin Mclean [mailto:jus...@classsoftware.com] > Envoyé : jeudi 26 septembre 2013 15:12 > À : dev@flex.apache.org > Objet : Re: Building the SDK from git > > Hi, > > With TLF environment variables work fine. > > On OSX I have the following: > TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ > AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/ > PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ > FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe Flash Builder > 4.6/Apache Flex/in/player/11.1/mac/Flash Player > Debugger.app/Contents/MacOS/Flash Player Debugger > PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel > Bender Toolkit 2/ ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension > Manager CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension > Manager CS5 ANT_HOME=/usr/share/ant > > My flex home is: > /Users/justinmclean/Documents/ApacheFlexDevelopGit > > Not all of these are required to be set to build the SDK, but are required to > make a release and/or run the mustella tests. > > You're correct about the build.properties files I've updated the values in > that and checked into develop. > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
RE: Building the SDK from git
Also, I noticed .actionScriptProperties and .flexLibProperties are missing from framework/projects/experimental Not committed or is it on purpose ? Maurice -Message d'origine- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 26 septembre 2013 15:12 À : dev@flex.apache.org Objet : Re: Building the SDK from git Hi, With TLF environment variables work fine. On OSX I have the following: TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/ PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex/in/player/11.1/mac/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 ANT_HOME=/usr/share/ant My flex home is: /Users/justinmclean/Documents/ApacheFlexDevelopGit Not all of these are required to be set to build the SDK, but are required to make a release and/or run the mustella tests. You're correct about the build.properties files I've updated the values in that and checked into develop. Thanks, Justin
Re: Building the SDK from git
Hi, > Which source is the most up-to-date ? You want the develop branches of both the SDK and TLF. Thanks, Justin
Re: Building the SDK from git
Hi, With TLF environment variables work fine. On OSX I have the following: TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ AIR_HOME=/Users/justinmclean/Documents/air/mac/3.1/ PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ FLASHPLAYER_DEBUGGER=/Users/justinmclean/Documents/Adobe Flash Builder 4.6/Apache Flex/in/player/11.1/mac/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 ANT_HOME=/usr/share/ant My flex home is: /Users/justinmclean/Documents/ApacheFlexDevelopGit Not all of these are required to be set to build the SDK, but are required to make a release and/or run the mustella tests. You're correct about the build.properties files I've updated the values in that and checked into develop. Thanks, Justin
RE: Building the SDK from git
I believe the wiki ones are still the good default set. They were done that way to match the repo names and are setup to use relative pathing between the two repos. It really doesn't matter which style you use, but you don't need to use both. My personal choice is using the repo names and using system vars in the OS to configure all the pathing. It allows me to sync around my flex development folders between my different pc's and have it use the current pc's pathing. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Thursday, September 26, 2013 8:37 AM To: dev@flex.apache.org Subject: RE: Building the SDK from git I have started reading the wiki on "Setting up Manually", and it says : TLF: git clone [https://git-wip-us.apache.org/repos/asf/flex-tlf.git] flex-tlf SDK: git clone [https://git-wip-us.apache.org/repos/asf/flex-sdk.git] flex-sdk However, http://flex.apache.org/dev-sourcecode.html says: git clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git sdk cd sdk git checkout develop You will also need: git clone https://git-wip-us.apache.org/repos/asf/flex-tlf.git tlf See the README at the root of the sdk for further details on how to set it up. And the *README* file says the same. - Which source is the most up-to-date ? Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : jeudi 26 septembre 2013 14:11 À : dev@flex.apache.org Objet : RE: Building the SDK from git I use... [anypath]/flex-sdk [anypath]/flex-tlf Just the default folder naming. Fred can tell you how to rename/move change things to fully customize the pathing layout. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Thursday, September 26, 2013 8:04 AM To: dev@flex.apache.org Subject: RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
My .gitconfig has only two lines, name and email. :-( I will read https://git-wip-us.apache.org/#contents to set the correct options. Thanks Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : jeudi 26 septembre 2013 14:45 À : dev@flex.apache.org Objet : RE: Building the SDK from git Both are good, the build script is able to take either flex-sdk or sdk, flex-tlf or tlf but you can have troubles run the script if at your first checkout the "autocrlf" in your /.gitconfig was not set to "input" -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:37 À : dev@flex.apache.org Objet : RE: Building the SDK from git I have started reading the wiki on "Setting up Manually", and it says : TLF: git clone [https://git-wip-us.apache.org/repos/asf/flex-tlf.git] flex-tlf SDK: git clone [https://git-wip-us.apache.org/repos/asf/flex-sdk.git] flex-sdk However, http://flex.apache.org/dev-sourcecode.html says: git clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git sdk cd sdk git checkout develop You will also need: git clone https://git-wip-us.apache.org/repos/asf/flex-tlf.git tlf See the README at the root of the sdk for further details on how to set it up. And the *README* file says the same. - Which source is the most up-to-date ? Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : jeudi 26 septembre 2013 14:11 À : dev@flex.apache.org Objet : RE: Building the SDK from git I use... [anypath]/flex-sdk [anypath]/flex-tlf Just the default folder naming. Fred can tell you how to rename/move change things to fully customize the pathing layout. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Thursday, September 26, 2013 8:04 AM To: dev@flex.apache.org Subject: RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
Both are good, the build script is able to take either flex-sdk or sdk, flex-tlf or tlf but you can have troubles run the script if at your first checkout the "autocrlf" in your /.gitconfig was not set to "input" -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:37 À : dev@flex.apache.org Objet : RE: Building the SDK from git I have started reading the wiki on "Setting up Manually", and it says : TLF: git clone [https://git-wip-us.apache.org/repos/asf/flex-tlf.git] flex-tlf SDK: git clone [https://git-wip-us.apache.org/repos/asf/flex-sdk.git] flex-sdk However, http://flex.apache.org/dev-sourcecode.html says: git clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git sdk cd sdk git checkout develop You will also need: git clone https://git-wip-us.apache.org/repos/asf/flex-tlf.git tlf See the README at the root of the sdk for further details on how to set it up. And the *README* file says the same. - Which source is the most up-to-date ? Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : jeudi 26 septembre 2013 14:11 À : dev@flex.apache.org Objet : RE: Building the SDK from git I use... [anypath]/flex-sdk [anypath]/flex-tlf Just the default folder naming. Fred can tell you how to rename/move change things to fully customize the pathing layout. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Thursday, September 26, 2013 8:04 AM To: dev@flex.apache.org Subject: RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
https://git-wip-us.apache.org/#contents -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:31 À : dev@flex.apache.org Objet : RE: Building the SDK from git Yes, I am on the develop branch. I have also read the basic docs on git since I am new to git ( they are very well written). "the wiki will tell you how to configure git" You mean " https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+Wiki"; ? OK, I will read it. Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : jeudi 26 septembre 2013 14:27 À : dev@flex.apache.org Objet : RE: Building the SDK from git Also, be sure to be on the develop branch "git checkout develop" and the wiki will tell you how to configure git, this is important for line ending for example. -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:04 À : dev@flex.apache.org Objet : RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
I have started reading the wiki on "Setting up Manually", and it says : TLF: git clone [https://git-wip-us.apache.org/repos/asf/flex-tlf.git] flex-tlf SDK: git clone [https://git-wip-us.apache.org/repos/asf/flex-sdk.git] flex-sdk However, http://flex.apache.org/dev-sourcecode.html says: git clone https://git-wip-us.apache.org/repos/asf/flex-sdk.git sdk cd sdk git checkout develop You will also need: git clone https://git-wip-us.apache.org/repos/asf/flex-tlf.git tlf See the README at the root of the sdk for further details on how to set it up. And the *README* file says the same. - Which source is the most up-to-date ? Maurice -Message d'origine- De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil] Envoyé : jeudi 26 septembre 2013 14:11 À : dev@flex.apache.org Objet : RE: Building the SDK from git I use... [anypath]/flex-sdk [anypath]/flex-tlf Just the default folder naming. Fred can tell you how to rename/move change things to fully customize the pathing layout. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Thursday, September 26, 2013 8:04 AM To: dev@flex.apache.org Subject: RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
Yes, I am on the develop branch. I have also read the basic docs on git since I am new to git ( they are very well written). "the wiki will tell you how to configure git" You mean " https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+Wiki"; ? OK, I will read it. Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : jeudi 26 septembre 2013 14:27 À : dev@flex.apache.org Objet : RE: Building the SDK from git Also, be sure to be on the develop branch "git checkout develop" and the wiki will tell you how to configure git, this is important for line ending for example. -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:04 À : dev@flex.apache.org Objet : RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
Thanks Fred, I will continue to post questions on the ML for others. Please ignore them until this week-end :-). Maurice -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : jeudi 26 septembre 2013 14:24 À : dev@flex.apache.org Objet : RE: Building the SDK from git I'll be able to help you more during the week end but in between, this is how I set my SDK: F:/sources/apache/flex/ sdk/ tlf/ My env.properties: env.AIR_HOME=F:\\sources\\adobe\\air\\3.4 env.FLASHPLAYER_DEBUGGER=C:\\Program Files (x86)\\Adobe\\Adobe Flash Builder 4.6\\player\\win\\11.1\\FlashPlayerDebugger.exe env.PLAYERGLOBAL_HOME=F:\\sources\\adobe\\playerglobal\\player env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 env.ADOBE_EXTENSION_MANAGER=C:\\Program Files (x86)\\Adobe\\Adobe Extension Manager CS5\\Adobe Extension Manager CS5.exe My mustella/local.properties sdk.dir=F:/sources/apache/flex/sdk shell=C:/cygwin64/bin/sh.exe -Fred -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:04 À : dev@flex.apache.org Objet : RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
Also, be sure to be on the develop branch "git checkout develop" and the wiki will tell you how to configure git, this is important for line ending for example. -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:04 À : dev@flex.apache.org Objet : RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
Something else: Build fails with the following error: " Could not load definitions from resource flexTasks.tasks. It could not be found." Main build.xml says: Does this mean modules/antTasks must be built prior to building or SDK? Maurice -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:04 À : dev@flex.apache.org Objet : RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
I'll be able to help you more during the week end but in between, this is how I set my SDK: F:/sources/apache/flex/ sdk/ tlf/ My env.properties: env.AIR_HOME=F:\\sources\\adobe\\air\\3.4 env.FLASHPLAYER_DEBUGGER=C:\\Program Files (x86)\\Adobe\\Adobe Flash Builder 4.6\\player\\win\\11.1\\FlashPlayerDebugger.exe env.PLAYERGLOBAL_HOME=F:\\sources\\adobe\\playerglobal\\player env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2 env.ADOBE_EXTENSION_MANAGER=C:\\Program Files (x86)\\Adobe\\Adobe Extension Manager CS5\\Adobe Extension Manager CS5.exe My mustella/local.properties sdk.dir=F:/sources/apache/flex/sdk shell=C:/cygwin64/bin/sh.exe -Fred -Message d'origine- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 14:04 À : dev@flex.apache.org Objet : RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
I use... [anypath]/flex-sdk [anypath]/flex-tlf Just the default folder naming. Fred can tell you how to rename/move change things to fully customize the pathing layout. -Mark -Original Message- From: Maurice Amsellem [mailto:maurice.amsel...@systar.com] Sent: Thursday, September 26, 2013 8:04 AM To: dev@flex.apache.org Subject: RE: Building the SDK from git Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
RE: Building the SDK from git
Actually, the README says that TLF_HOME is optional if the tlf directory is a sibling of sdk. This is my directory configuration: ApacheFlex/git_source/ sdk/ tlf/ And I still get an error when running the build "TLF_HOME is not defined". Maurice De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 26 septembre 2013 13:54 À : dev@flex.apache.org Objet : Building the SDK from git Hi, I am trying to build the develop SDK from git. So I followed the instructions in the README file, and noticed some things that seem not to be as expected: 1) README says you can set PLAYERGLOBAL_HOME, ..., TLF_HOME in env.properties. All vars are referenced and explained in env-template.properties, except TLF_HOME 2) Build.properties says release.version = 4.10.0, air.version = 3.7 and playerglobal.version=11.1. Shouldn't it be 3.8 and 11.8 ? What do you think? Maurice Maurice Amsellem SYSTAR R&D - BusinessBridgeFX [Description : Telephone:] +33(0)1 49 11 45 62 / [Description : Mobile Phone:] +33(0)6 07 48 95 43
Re: Building the SDK
On 9/2/13 12:45 PM, "Harbs" wrote: >If I'm not mistaken, building the sdk works, but building tlf directly >does not work if the sdk is not named flex-sdk. > >This is a line from build.xml in TLF: > > >Of course this could be overridden, but keeping the same directory names >can't be a bad ideaŠ ;-) Are you just running ant from the tlf repo? Honestly, I haven't really tested it so there could be issues. I just use ant from flex-sdk/frameworks/projects/textLayout. Running ant in tlf runs a lot more than I need right now... -Alex
RE: Building the SDK
I don't know but to me, doing [myDevDisk]:/sources/apache/flex/sdk allows me to keep my source tree clean / clear having more opened/closed source projects. -Fred -Message d'origine- De : Mark Kessler [mailto:kesslerconsult...@gmail.com] Envoyé : lundi 2 septembre 2013 22:03 À : Dev@Flex Objet : Re: Building the SDK Am I the only person who just dumps all my GIT repo sources into a simple root folder GIT\Flex-SDK and GIT\Flex-TLF ? -Mark On Mon, Sep 2, 2013 at 3:56 PM, Frédéric THOMAS wrote: > Ok, so, it is easy to make it accept other names, actually, we have > flex-sdk and sdk, doing so is more flexible, personally, I don't like > to have names repeating themselves in my path, I wouldn't like to have > apache/flex/flex-sdk, I rather prefer to have apache/flex/sdk. > > I'll change that tomorrow if nobody disagree. > > -Fred >
Re: Building the SDK
Am I the only person who just dumps all my GIT repo sources into a simple root folder GIT\Flex-SDK and GIT\Flex-TLF ? -Mark On Mon, Sep 2, 2013 at 3:56 PM, Frédéric THOMAS wrote: > Ok, so, it is easy to make it accept other names, actually, we have > flex-sdk > and sdk, doing so is more flexible, personally, I don't like to have names > repeating themselves in my path, I wouldn't like to have > apache/flex/flex-sdk, I rather prefer to have apache/flex/sdk. > > I'll change that tomorrow if nobody disagree. > > -Fred >
RE: Building the SDK
Ok, so, it is easy to make it accept other names, actually, we have flex-sdk and sdk, doing so is more flexible, personally, I don't like to have names repeating themselves in my path, I wouldn't like to have apache/flex/flex-sdk, I rather prefer to have apache/flex/sdk. I'll change that tomorrow if nobody disagree. -Fred -Message d'origine- De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : lundi 2 septembre 2013 21:46 À : dev@flex.apache.org Objet : Re: Building the SDK If I'm not mistaken, building the sdk works, but building tlf directly does not work if the sdk is not named flex-sdk. This is a line from build.xml in TLF: Of course this could be overridden, but keeping the same directory names can't be a bad idea ;-) On Sep 2, 2013, at 10:17 PM, Frédéric THOMAS wrote: > I cloned flex-sdk to sdk, flex-tlf to tlf and had no problems to build > the sdk. > > The only problem was to build falcon, I had to modify the build.xml to > accept either flex-sdk or sdk and add local.properties to the .gitignore. > I've been able to run ant and ant eclipse, did not try with > falcon.js/jx yet > > If nobody has problems with that, I'll commit it tomorrow. > > -Fred > > -Message d'origine- > De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : lundi 2 > septembre 2013 17:12 À : dev@flex.apache.org Objet : RE: Building the > SDK > > Harbs, > > I'm in the process to install the SDK + TLF + others, before my dir > structure was apache/flex/sdk, apache/flex/tlf and was working pretty > well, it wasn't mandatory to have flex-sdk or flex-tlf, so, if you let > me finish, I'll be able to tell you how it went. > > -Fred > > -Message d'origine- > De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : lundi 2 septembre > 2013 > 17:07 À : dev@flex.apache.org Objet : Re: Building the SDK > >> First question: Are you using the develop branch in TLF? And building by >> just running "ant" from the sdk's textLayout folder? I'm not having >> these issues. I don't know what will happen if you run the build.xml >> in the TLF repo. I've never done it. > > Yes. That's right. > > The missing type declaration seems to be a real error. I'm not sure > whether the others are real issues or not. > I have not problems ignoring the warnings, but if they are real, might > as well fix them ;-)
Re: Building the SDK
If I'm not mistaken, building the sdk works, but building tlf directly does not work if the sdk is not named flex-sdk. This is a line from build.xml in TLF: Of course this could be overridden, but keeping the same directory names can't be a bad idea… ;-) On Sep 2, 2013, at 10:17 PM, Frédéric THOMAS wrote: > I cloned flex-sdk to sdk, flex-tlf to tlf and had no problems to build the > sdk. > > The only problem was to build falcon, I had to modify the build.xml to > accept either flex-sdk or sdk and add local.properties to the .gitignore. > I've been able to run ant and ant eclipse, did not try with falcon.js/jx yet > > If nobody has problems with that, I'll commit it tomorrow. > > -Fred > > -Message d'origine- > De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] > Envoyé : lundi 2 septembre 2013 17:12 > À : dev@flex.apache.org > Objet : RE: Building the SDK > > Harbs, > > I'm in the process to install the SDK + TLF + others, before my dir > structure was apache/flex/sdk, apache/flex/tlf and was working pretty well, > it wasn't mandatory to have flex-sdk or flex-tlf, so, if you let me finish, > I'll be able to tell you how it went. > > -Fred > > -Message d'origine- > De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : lundi 2 septembre 2013 > 17:07 À : dev@flex.apache.org Objet : Re: Building the SDK > >> First question: Are you using the develop branch in TLF? And building by >> just running "ant" from the sdk's textLayout folder? I'm not having >> these issues. I don't know what will happen if you run the build.xml >> in the TLF repo. I've never done it. > > Yes. That's right. > > The missing type declaration seems to be a real error. I'm not sure whether > the others are real issues or not. > I have not problems ignoring the warnings, but if they are real, might as > well fix them… ;-)
RE: Building the SDK
I cloned flex-sdk to sdk, flex-tlf to tlf and had no problems to build the sdk. The only problem was to build falcon, I had to modify the build.xml to accept either flex-sdk or sdk and add local.properties to the .gitignore. I've been able to run ant and ant eclipse, did not try with falcon.js/jx yet If nobody has problems with that, I'll commit it tomorrow. -Fred -Message d'origine- De : Frédéric THOMAS [mailto:webdoubl...@hotmail.com] Envoyé : lundi 2 septembre 2013 17:12 À : dev@flex.apache.org Objet : RE: Building the SDK Harbs, I'm in the process to install the SDK + TLF + others, before my dir structure was apache/flex/sdk, apache/flex/tlf and was working pretty well, it wasn't mandatory to have flex-sdk or flex-tlf, so, if you let me finish, I'll be able to tell you how it went. -Fred -Message d'origine- De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : lundi 2 septembre 2013 17:07 À : dev@flex.apache.org Objet : Re: Building the SDK > First question: Are you using the develop branch in TLF? And building by > just running "ant" from the sdk's textLayout folder? I'm not having > these issues. I don't know what will happen if you run the build.xml > in the TLF repo. I've never done it. Yes. That's right. The missing type declaration seems to be a real error. I'm not sure whether the others are real issues or not. I have not problems ignoring the warnings, but if they are real, might as well fix them ;-)
RE: Building the SDK
Harbs, I'm in the process to install the SDK + TLF + others, before my dir structure was apache/flex/sdk, apache/flex/tlf and was working pretty well, it wasn't mandatory to have flex-sdk or flex-tlf, so, if you let me finish, I'll be able to tell you how it went. -Fred -Message d'origine- De : Harbs [mailto:harbs.li...@gmail.com] Envoyé : lundi 2 septembre 2013 17:07 À : dev@flex.apache.org Objet : Re: Building the SDK > First question: Are you using the develop branch in TLF? And building by > just running "ant" from the sdk's textLayout folder? I'm not having > these issues. I don't know what will happen if you run the build.xml > in the TLF repo. I've never done it. Yes. That's right. The missing type declaration seems to be a real error. I'm not sure whether the others are real issues or not. I have not problems ignoring the warnings, but if they are real, might as well fix them ;-)
Re: Building the SDK
> First question: Are you using the develop branch in TLF? And building by > just running "ant" from the sdk's textLayout folder? I'm not having > these issues. I don't know what will happen if you run the build.xml in > the TLF repo. I've never done it. Yes. That's right. The missing type declaration seems to be a real error. I'm not sure whether the others are real issues or not. I have not problems ignoring the warnings, but if they are real, might as well fix them… ;-)
Re: Building the SDK
On 9/2/13 6:05 AM, "Harbs" wrote: >BTW, I get a number of build warnings when building tlf: >1) ParagraphElement has two places where currentAtomIndex has no type >declaration. >2) A bunch of calls to TextLine.flushAtomData() does nothing. >3) A couple of these warnings: ApplyElementStyleNameOperation' has been >deprecated. Please use 'ApplyFormatToElementOperation' These warnings >are in EditClasses. > >I see no reason to not correct #1. I'm not sure about #2 and #3. First question: Are you using the develop branch in TLF? And building by just running "ant" from the sdk's textLayout folder? I'm not having these issues. I don't know what will happen if you run the build.xml in the TLF repo. I've never done it. -Alex
Re: Building the SDK
On 9/2/13 5:26 AM, "Harbs" wrote: > >You should now be able to edit and debug the TLF source. When you rebuild >the swc after editing the source, the correct swc should be linked. > >You will need to repeat steps 8-11 for every project you want to debug >tlf code with. > >HTH, >Harbs > >P.S. Should I write these steps up on the wiki or something? Sure, feel free to add to the wiki. -Alex
Re: Building the SDK
BTW, I get a number of build warnings when building tlf: 1) ParagraphElement has two places where currentAtomIndex has no type declaration. 2) A bunch of calls to TextLine.flushAtomData() does nothing. 3) A couple of these warnings: ApplyElementStyleNameOperation' has been deprecated. Please use 'ApplyFormatToElementOperation' These warnings are in EditClasses. I see no reason to not correct #1. I'm not sure about #2 and #3. On Sep 2, 2013, at 3:26 PM, Harbs wrote: > Okie Dokie! > > I'm finally up and running. Here's what I did in case it's useful to someone > else having trouble with this: > > 1) Make sure your local repro names match the origin repro names exactly. > (i.e. they should be called "flex-sdk" and "flex-tlf"). > 2) Makes sure the repros are both in the same parent folder. > 3) Download the dependencies and put them somewhere on your machine. > 4) In the flex-sdk copy the env-template.properties file and rename it to > env.properties. > 5) Set the environment variables in that file. Here's what mine look like: > env.AIR_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/AdobeAIRSDK/ > env.TLF_HOME=/Users/harbs/Documents/ApacheFlex/git/flex-tlf/ > > env.PLAYERGLOBAL_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/player/ > env.PIXELBENDER_HOME=/Applications/Utilities/Adobe > Utilities-CS5.localized/Pixel Bender Toolkit 2/ > 6) Build the flex-sdk (cd [your sdk path] and then just run ant) > 7) Once the flex sdk is built, you should be able to build the tlf sdk by > itself (that takes between 10 and 20 seconds rather than that amount of time > in minutes…) > 8) In Flash Builder set the SDK or your project to "Flex Develop" or whatever > you want to call the SDK that you just built. > 9) Remove the playerglobal reference because it will likely not be linked > correctly, and link a valid one on your machine. > 10 Remove the reference in the project to textLayout.swc in the "Flex > Develop" sdk and add the one in flex-tlf/bin. > 11) Select the textLayout.swc file that you linked to in the flex-tlf repro > and set the properties of that (project) reference to flex-tlf/textLayout/src > > You should now be able to edit and debug the TLF source. When you rebuild the > swc after editing the source, the correct swc should be linked. > > You will need to repeat steps 8-11 for every project you want to debug tlf > code with. > > HTH, > Harbs > > P.S. Should I write these steps up on the wiki or something? > > On Sep 2, 2013, at 9:53 AM, Harbs wrote: > >> Okay. Thanks. >> >> I'll give it another go later today… >> >> On Sep 2, 2013, at 9:22 AM, Alex Harui wrote: >> >>> >>> >>> On 9/1/13 10:57 PM, "Harbs" wrote: >>> I'm going around in circles hereŠ I have two problems. One with playerglobal.swc and another with textLayout.swc 1) When I link the develop SDK to a project, I get two swc links: playerglobal.swc and "11.1". It can't find either of those. I can manage to get the SDK to work by unlinking those and linking to a valid copy of playerglobal on my machine. This is workable, but I'm concerned by why I need to do that. It's also a pain to do this every time I want to use the dev sdkŠ >>> I just realized that this sort of thing is why we don't use the git repo >>> folders as-is in FB. That's why we have the Installer and those scripts >>> like makeApacheFlexForFLexBuilder. And why I don't use FB and just use >>> the command line for MXMLC and FDB. >>> >>> I guess I'd suggest using the Installer to set up a working SDK then copy >>> textLayout.swc into the working SDK's frameworks/libs folder. But even >>> then, I think you have to worry about FB caching the SWC. >>> >>> HTH, >>> -Alex >>> >>> >> >
Re: Building the SDK
Okie Dokie! I'm finally up and running. Here's what I did in case it's useful to someone else having trouble with this: 1) Make sure your local repro names match the origin repro names exactly. (i.e. they should be called "flex-sdk" and "flex-tlf"). 2) Makes sure the repros are both in the same parent folder. 3) Download the dependencies and put them somewhere on your machine. 4) In the flex-sdk copy the env-template.properties file and rename it to env.properties. 5) Set the environment variables in that file. Here's what mine look like: env.AIR_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/AdobeAIRSDK/ env.TLF_HOME=/Users/harbs/Documents/ApacheFlex/git/flex-tlf/ env.PLAYERGLOBAL_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/player/ env.PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ 6) Build the flex-sdk (cd [your sdk path] and then just run ant) 7) Once the flex sdk is built, you should be able to build the tlf sdk by itself (that takes between 10 and 20 seconds rather than that amount of time in minutes…) 8) In Flash Builder set the SDK or your project to "Flex Develop" or whatever you want to call the SDK that you just built. 9) Remove the playerglobal reference because it will likely not be linked correctly, and link a valid one on your machine. 10 Remove the reference in the project to textLayout.swc in the "Flex Develop" sdk and add the one in flex-tlf/bin. 11) Select the textLayout.swc file that you linked to in the flex-tlf repro and set the properties of that (project) reference to flex-tlf/textLayout/src You should now be able to edit and debug the TLF source. When you rebuild the swc after editing the source, the correct swc should be linked. You will need to repeat steps 8-11 for every project you want to debug tlf code with. HTH, Harbs P.S. Should I write these steps up on the wiki or something? On Sep 2, 2013, at 9:53 AM, Harbs wrote: > Okay. Thanks. > > I'll give it another go later today… > > On Sep 2, 2013, at 9:22 AM, Alex Harui wrote: > >> >> >> On 9/1/13 10:57 PM, "Harbs" wrote: >> >>> I'm going around in circles hereŠ >>> >>> I have two problems. One with playerglobal.swc and another with >>> textLayout.swc >>> >>> 1) When I link the develop SDK to a project, I get two swc links: >>> playerglobal.swc and "11.1". It can't find either of those. I can manage >>> to get the SDK to work by unlinking those and linking to a valid copy of >>> playerglobal on my machine. This is workable, but I'm concerned by why I >>> need to do that. It's also a pain to do this every time I want to use the >>> dev sdkŠ >> I just realized that this sort of thing is why we don't use the git repo >> folders as-is in FB. That's why we have the Installer and those scripts >> like makeApacheFlexForFLexBuilder. And why I don't use FB and just use >> the command line for MXMLC and FDB. >> >> I guess I'd suggest using the Installer to set up a working SDK then copy >> textLayout.swc into the working SDK's frameworks/libs folder. But even >> then, I think you have to worry about FB caching the SWC. >> >> HTH, >> -Alex >> >> >
Re: Building the SDK
Okay. Thanks. I'll give it another go later today… On Sep 2, 2013, at 9:22 AM, Alex Harui wrote: > > > On 9/1/13 10:57 PM, "Harbs" wrote: > >> I'm going around in circles hereŠ >> >> I have two problems. One with playerglobal.swc and another with >> textLayout.swc >> >> 1) When I link the develop SDK to a project, I get two swc links: >> playerglobal.swc and "11.1". It can't find either of those. I can manage >> to get the SDK to work by unlinking those and linking to a valid copy of >> playerglobal on my machine. This is workable, but I'm concerned by why I >> need to do that. It's also a pain to do this every time I want to use the >> dev sdkŠ > I just realized that this sort of thing is why we don't use the git repo > folders as-is in FB. That's why we have the Installer and those scripts > like makeApacheFlexForFLexBuilder. And why I don't use FB and just use > the command line for MXMLC and FDB. > > I guess I'd suggest using the Installer to set up a working SDK then copy > textLayout.swc into the working SDK's frameworks/libs folder. But even > then, I think you have to worry about FB caching the SWC. > > HTH, > -Alex > >
Re: Building the SDK
Hi, > I guess I'd suggest using the Installer to set up a working SDK then copy > textLayout.swc into the working SDK's frameworks/libs folder. But even > then, I think you have to worry about FB caching the SWC. From my experience it doesn't cache the framework swcs that often (generally a ant in a project directory will be picked up by FB). On the rare occasion it does changing the project's SDK to another and then back again refreshes/resets the cache. Justin
Re: Building the SDK
On 9/1/13 10:57 PM, "Harbs" wrote: >I'm going around in circles hereŠ > >I have two problems. One with playerglobal.swc and another with >textLayout.swc > >1) When I link the develop SDK to a project, I get two swc links: >playerglobal.swc and "11.1". It can't find either of those. I can manage >to get the SDK to work by unlinking those and linking to a valid copy of >playerglobal on my machine. This is workable, but I'm concerned by why I >need to do that. It's also a pain to do this every time I want to use the >dev sdkŠ I just realized that this sort of thing is why we don't use the git repo folders as-is in FB. That's why we have the Installer and those scripts like makeApacheFlexForFLexBuilder. And why I don't use FB and just use the command line for MXMLC and FDB. I guess I'd suggest using the Installer to set up a working SDK then copy textLayout.swc into the working SDK's frameworks/libs folder. But even then, I think you have to worry about FB caching the SWC. HTH, -Alex
Re: Building the SDK
On 9/1/13 10:59 PM, "Harbs" wrote: >Okay. How do I do that? > >You are referring to build.xml in the tlf folder. Right? No. I've tried to do that and never figured it out. Instead: 1) Go to Project/Properties/Build Paths 2) Open the SDK folder 3) Open the textLayout.swc entry 4) Click on Source Attachment 5) Click Edit button on the right and set it properly. > >On Sep 2, 2013, at 8:50 AM, Alex Harui wrote: > >> On second thought, you may need to set up the source attachment in your >> build properties. >
Re: Building the SDK
Here's what I see in the build.xml: IMXMLObject Where is the source directory defined? On Sep 2, 2013, at 8:59 AM, Harbs wrote: > Okay. How do I do that? > > You are referring to build.xml in the tlf folder. Right? > > On Sep 2, 2013, at 8:50 AM, Alex Harui wrote: > >> On second thought, you may need to set up the source attachment in your >> build properties. >
Re: Building the SDK
Okay. How do I do that? You are referring to build.xml in the tlf folder. Right? On Sep 2, 2013, at 8:50 AM, Alex Harui wrote: > On second thought, you may need to set up the source attachment in your > build properties.
Re: Building the SDK
I'm going around in circles here… I have two problems. One with playerglobal.swc and another with textLayout.swc 1) When I link the develop SDK to a project, I get two swc links: playerglobal.swc and "11.1". It can't find either of those. I can manage to get the SDK to work by unlinking those and linking to a valid copy of playerglobal on my machine. This is workable, but I'm concerned by why I need to do that. It's also a pain to do this every time I want to use the dev sdk… 2) textLayout.swc works, but I does not get linked to source. When I try to jump to the source of any TLF classes I get an error that the source cannot be found. I tried linking to textLayout.swc in the tlf folder instead and I have the same problem. I'm able to recompile and test my changes, but I can't do any real debugging if it does not link to the source… Any ideas on how I can fix this? Harbs On Sep 2, 2013, at 8:30 AM, Alex Harui wrote: > > > On 9/1/13 10:21 PM, "Harbs" wrote: > >> Okay. Makes sense. >> >> And how do you set breakpoints in the code? > I'm not using FB. FDB allows me to set breakpoints just fine. FB should > too given that it will use the path in the SWC that you built on your > machine so it should be an exact match. >> >> Does it make sense to include the swcs in the TLF folder instead of the >> ones in the sdk folder? > The build script in flex-sdk/frameworks/projects/textLayout should copy > the SWCs from wherever flex-tlf puts it. > > -Alex >
Re: Building the SDK
On 9/1/13 10:30 PM, "Alex Harui" wrote: > > >On 9/1/13 10:21 PM, "Harbs" wrote: > >>Okay. Makes sense. >> >>And how do you set breakpoints in the code? >I'm not using FB. FDB allows me to set breakpoints just fine. FB should >too given that it will use the path in the SWC that you built on your >machine so it should be an exact match. On second thought, you may need to set up the source attachment in your build properties. >> >>Does it make sense to include the swcs in the TLF folder instead of the >>ones in the sdk folder? >The build script in flex-sdk/frameworks/projects/textLayout should copy >the SWCs from wherever flex-tlf puts it. > >-Alex >
Re: Building the SDK
On 9/1/13 10:21 PM, "Harbs" wrote: >Okay. Makes sense. > >And how do you set breakpoints in the code? I'm not using FB. FDB allows me to set breakpoints just fine. FB should too given that it will use the path in the SWC that you built on your machine so it should be an exact match. > >Does it make sense to include the swcs in the TLF folder instead of the >ones in the sdk folder? The build script in flex-sdk/frameworks/projects/textLayout should copy the SWCs from wherever flex-tlf puts it. -Alex
Re: Building the SDK
Okay. Makes sense. And how do you set breakpoints in the code? Does it make sense to include the swcs in the TLF folder instead of the ones in the sdk folder? On Sep 2, 2013, at 6:29 AM, Alex Harui wrote: > > > On 9/1/13 3:07 PM, "Harbs" wrote: > >> So how does Flash Builder know where the source is? > IIRC, when we package up everything for a release, we copy the TLF code > into the frameworks/projects/textLayout folder. > > But because we had problems with Git handling the mapping of source from > the flex-tlf repo into the flex-sdk repo, when developing, we leave the > source separate. > > FWIW, my workflow in the TLF work I did was to make changes in > flex-tlf/textLayout/src, run ant from the > flex-sdk/frameworks/projects/textLayout then re-compile the test case. Of > course, I wasn't using FB which might cache the SWC and require restarts > after each ant run. > >> >> On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote: >> >>> Hi, >>> Is the TLF source files supposed to be copied to the flex sdk folder when building the sdk? >>> No, it's left where it is. >>> >>> Justin >>> >> >
Re: Building the SDK
On 9/1/13 3:07 PM, "Harbs" wrote: >So how does Flash Builder know where the source is? IIRC, when we package up everything for a release, we copy the TLF code into the frameworks/projects/textLayout folder. But because we had problems with Git handling the mapping of source from the flex-tlf repo into the flex-sdk repo, when developing, we leave the source separate. FWIW, my workflow in the TLF work I did was to make changes in flex-tlf/textLayout/src, run ant from the flex-sdk/frameworks/projects/textLayout then re-compile the test case. Of course, I wasn't using FB which might cache the SWC and require restarts after each ant run. > >On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote: > >> Hi, >> >>> Is the TLF source files supposed to be copied to the flex sdk folder >>>when building the sdk? >> No, it's left where it is. >> >> Justin >> >
Re: Building the SDK
So how does Flash Builder know where the source is? On Sep 2, 2013, at 12:58 AM, Justin Mclean wrote: > Hi, > >> Is the TLF source files supposed to be copied to the flex sdk folder when >> building the sdk? > No, it's left where it is. > > Justin >
Re: Building the SDK
Hi, > Is the TLF source files supposed to be copied to the flex sdk folder when > building the sdk? No, it's left where it is. Justin
Re: Building the SDK
I think so. I added it to the env.properties file. I believe it's working because otherwise I would not get the textLayout.swc files. No? Here's my env.properties file (in flex-sdk -- minus all the comments…) env.AIR_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/AdobeAIRSDK/ env.TLF_HOME=/Users/harbs/Documents/ApacheFlex/git/flex-tlf/ env.PLAYERGLOBAL_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/player/ env.PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ Is the TLF source files supposed to be copied to the flex sdk folder when building the sdk? On Sep 2, 2013, at 12:47 AM, Justin Mclean wrote: > HI, > >> I redid everything from scratch. Everything went smoother this time, but I >> still can not connect to the TLF source. > > Probably a silly question but is TLF_HOME correctly set? > > Justin
Re: Building the SDK
HI, > I redid everything from scratch. Everything went smoother this time, but I > still can not connect to the TLF source. Probably a silly question but is TLF_HOME correctly set? Justin
RE: Building the SDK
Look good to me, see
https://fisheye6.atlassian.com/browse/flex-sdk/frameworks/projects/textLayou
t/build.xml?r=4f20635628acdc09e8739c5f94ec644d20cbd959
-Message d'origine-
De : Harbs [mailto:harbs.li...@gmail.com]
Envoyé : dimanche 1 septembre 2013 23:35
À : dev@flex.apache.org
Objet : Re: Building the SDK
I redid everything from scratch. Everything went smoother this time, but I
still can not connect to the TLF source.
Here's what I have:
git
flex-tlf
--etc...
flex-sdk
frameworks
libs
textLayout.swc (along with all the other swcs)
player
(all the versions)
locale
en_US
textLayout_rb.swc (along with all the other rb swcs)
projects
textLayout (with no source -- all other projects have source.)
That seems logical to me since TLF is in another repro, but how is the SDK
supposed to find the TLF source?
Harbs
On Sep 1, 2013, at 11:09 PM, Harbs wrote:
> I have a feeling my problems might stem from the fact that my git repro is
named differently.
>
> I'm re-downloading the whole repro and starting from scratch with the
> standard names
>
> Tomorrow is another day
>
> On Sep 1, 2013, at 10:55 PM, Harbs wrote:
>
>> Okay. I solved this one, but I'm only getting source for core Flex
components. (i.e. I get source for Spark components, but I don't get source
for TLF stuff:
>> "Source could not be found for flashx.textLayout.edit.EditManager in
\Users\harbs\blabla\textLayout.swc"
>>
>> How do I properly link TLF to the rest of the SDK?
>>
>> On Sep 1, 2013, at 9:56 PM, Harbs wrote:
>>
>>> When specifying the paths in env.protperties, the spaces don't cause any
problems.
>>>
>>> But it looks like my issues are not finished. I get this error when I
try to actually use the SDK:
>>> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
SDK/frameworks//Users/harbs/Documents/Apache
Flex/Dependencies/player//11.1/playerglobal.swc'
>>>
>>> I'm not sure where I'm supposed to fix this (really wonky) path
>>>
>>> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>>>
>>>> I set all the variables in the env.properties file instead of via
>>>> the command line and that seems to have resolved the problem.
>>>> Weird
>>>>
>>>> Next time I'll try with the spaces and see what happens.
>>>>
>>>> Harbs
>>>>
>>>> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>>>>
>>>>> Use set command to dump environment. Maybe a hidden char in there?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>>>>>
>>>>> Harbs wrote:
>>>>>
>>>>>
>>>>> Still no go:
>>>>>
>>>>> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>>>>>
>>>>> check-playerglobal-home:
>>>>> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME} [echo]
>>>>> playerglobal.version is 11.1
>>>>>
>>>>> BUILD FAILED
>>>>> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
>>>>> environment variable PLAYERGLOBAL_HOME is not set to a directory
>>>>>
>>>>> Total time: 0 seconds
>>>>>
>>>>> It's been a while since I felt like such an idiot
;-)
>>>>>
>>>>> Maybe I'll try to restart my machine a bit later
>>>>>
>>>>> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> There's still a space in the path - try removing that? I know it was
an issue early on but thought it had been fixed - perhaps not.
>>>>>>
>>>>>>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>>>>>
>>>>>> Thanks,
>>>>>> Justin
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Building the SDK
I redid everything from scratch. Everything went smoother this time, but I
still can not connect to the TLF source.
Here's what I have:
git
flex-tlf
--etc...
flex-sdk
frameworks
libs
textLayout.swc (along with all the other swcs)
player
(all the versions)
locale
en_US
textLayout_rb.swc (along with all the other rb swcs)
projects
textLayout (with no source -- all other projects have source.)
That seems logical to me since TLF is in another repro, but how is the SDK
supposed to find the TLF source?
Harbs
On Sep 1, 2013, at 11:09 PM, Harbs wrote:
> I have a feeling my problems might stem from the fact that my git repro is
> named differently.
>
> I'm re-downloading the whole repro and starting from scratch with the
> standard names…
>
> Tomorrow is another day…
>
> On Sep 1, 2013, at 10:55 PM, Harbs wrote:
>
>> Okay. I solved this one, but I'm only getting source for core Flex
>> components. (i.e. I get source for Spark components, but I don't get source
>> for TLF stuff:
>> "Source could not be found for flashx.textLayout.edit.EditManager in
>> \Users\harbs\blabla\textLayout.swc"
>>
>> How do I properly link TLF to the rest of the SDK?
>>
>> On Sep 1, 2013, at 9:56 PM, Harbs wrote:
>>
>>> When specifying the paths in env.protperties, the spaces don't cause any
>>> problems.
>>>
>>> But it looks like my issues are not finished. I get this error when I try
>>> to actually use the SDK:
>>> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
>>> SDK/frameworks//Users/harbs/Documents/Apache
>>> Flex/Dependencies/player//11.1/playerglobal.swc'
>>>
>>> I'm not sure where I'm supposed to fix this (really wonky) path…
>>>
>>> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>>>
I set all the variables in the env.properties file instead of via the
command line and that seems to have resolved the problem. Weird…
Next time I'll try with the spaces and see what happens.
Harbs
On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
> Use set command to dump environment. Maybe a hidden char in there?
>
>
>
>
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Harbs wrote:
>
>
> Still no go:
>
> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>
> check-playerglobal-home:
> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
> [echo] playerglobal.version is 11.1
>
> BUILD FAILED
> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
> environment variable PLAYERGLOBAL_HOME is not set to a directory
>
> Total time: 0 seconds
>
> It's been a while since I felt like such an idiot… ;-)
>
> Maybe I'll try to restart my machine a bit later…
>
> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>
>> Hi,
>>
>> There's still a space in the path - try removing that? I know it was an
>> issue early on but thought it had been fixed - perhaps not.
>>
>>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>
>> Thanks,
>> Justin
>>
>>
>
>>>
>>
>
Re: Building the SDK
I have a feeling my problems might stem from the fact that my git repro is
named differently.
I'm re-downloading the whole repro and starting from scratch with the standard
names…
Tomorrow is another day…
On Sep 1, 2013, at 10:55 PM, Harbs wrote:
> Okay. I solved this one, but I'm only getting source for core Flex
> components. (i.e. I get source for Spark components, but I don't get source
> for TLF stuff:
> "Source could not be found for flashx.textLayout.edit.EditManager in
> \Users\harbs\blabla\textLayout.swc"
>
> How do I properly link TLF to the rest of the SDK?
>
> On Sep 1, 2013, at 9:56 PM, Harbs wrote:
>
>> When specifying the paths in env.protperties, the spaces don't cause any
>> problems.
>>
>> But it looks like my issues are not finished. I get this error when I try to
>> actually use the SDK:
>> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
>> SDK/frameworks//Users/harbs/Documents/Apache
>> Flex/Dependencies/player//11.1/playerglobal.swc'
>>
>> I'm not sure where I'm supposed to fix this (really wonky) path…
>>
>> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>>
>>> I set all the variables in the env.properties file instead of via the
>>> command line and that seems to have resolved the problem. Weird…
>>>
>>> Next time I'll try with the spaces and see what happens.
>>>
>>> Harbs
>>>
>>> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>>>
Use set command to dump environment. Maybe a hidden char in there?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Harbs wrote:
Still no go:
Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
environment variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
It's been a while since I felt like such an idiot… ;-)
Maybe I'll try to restart my machine a bit later…
On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
> Hi,
>
> There's still a space in the path - try removing that? I know it was an
> issue early on but thought it had been fixed - perhaps not.
>
>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>
> Thanks,
> Justin
>
>
>>>
>>
>
Re: Building the SDK
Okay. I solved this one, but I'm only getting source for core Flex components.
(i.e. I get source for Spark components, but I don't get source for TLF stuff:
"Source could not be found for flashx.textLayout.edit.EditManager in
\Users\harbs\blabla\textLayout.swc"
How do I properly link TLF to the rest of the SDK?
On Sep 1, 2013, at 9:56 PM, Harbs wrote:
> When specifying the paths in env.protperties, the spaces don't cause any
> problems.
>
> But it looks like my issues are not finished. I get this error when I try to
> actually use the SDK:
> unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
> SDK/frameworks//Users/harbs/Documents/Apache
> Flex/Dependencies/player//11.1/playerglobal.swc'
>
> I'm not sure where I'm supposed to fix this (really wonky) path…
>
> On Sep 1, 2013, at 8:20 PM, Harbs wrote:
>
>> I set all the variables in the env.properties file instead of via the
>> command line and that seems to have resolved the problem. Weird…
>>
>> Next time I'll try with the spaces and see what happens.
>>
>> Harbs
>>
>> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>>
>>> Use set command to dump environment. Maybe a hidden char in there?
>>>
>>>
>>>
>>>
>>> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>>>
>>> Harbs wrote:
>>>
>>>
>>> Still no go:
>>>
>>> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>>>
>>> check-playerglobal-home:
>>> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
>>> [echo] playerglobal.version is 11.1
>>>
>>> BUILD FAILED
>>> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The
>>> environment variable PLAYERGLOBAL_HOME is not set to a directory
>>>
>>> Total time: 0 seconds
>>>
>>> It's been a while since I felt like such an idiot… ;-)
>>>
>>> Maybe I'll try to restart my machine a bit later…
>>>
>>> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>>>
Hi,
There's still a space in the path - try removing that? I know it was an
issue early on but thought it had been fixed - perhaps not.
> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
Thanks,
Justin
>>>
>>
>
Re: Building the SDK
When specifying the paths in env.protperties, the spaces don't cause any
problems.
But it looks like my issues are not finished. I get this error when I try to
actually use the SDK:
unable to open '/Users/harbs/Documents/Apache Flex/git/Flex
SDK/frameworks//Users/harbs/Documents/Apache
Flex/Dependencies/player//11.1/playerglobal.swc'
I'm not sure where I'm supposed to fix this (really wonky) path…
On Sep 1, 2013, at 8:20 PM, Harbs wrote:
> I set all the variables in the env.properties file instead of via the command
> line and that seems to have resolved the problem. Weird…
>
> Next time I'll try with the spaces and see what happens.
>
> Harbs
>
> On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
>
>> Use set command to dump environment. Maybe a hidden char in there?
>>
>>
>>
>>
>> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>>
>> Harbs wrote:
>>
>>
>> Still no go:
>>
>> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>>
>> check-playerglobal-home:
>>[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
>>[echo] playerglobal.version is 11.1
>>
>> BUILD FAILED
>> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
>> variable PLAYERGLOBAL_HOME is not set to a directory
>>
>> Total time: 0 seconds
>>
>> It's been a while since I felt like such an idiot… ;-)
>>
>> Maybe I'll try to restart my machine a bit later…
>>
>> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>>
>>> Hi,
>>>
>>> There's still a space in the path - try removing that? I know it was an
>>> issue early on but thought it had been fixed - perhaps not.
>>>
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>>
>>> Thanks,
>>> Justin
>>>
>>>
>>
>
Re: Building the SDK
I set all the variables in the env.properties file instead of via the command
line and that seems to have resolved the problem. Weird…
Next time I'll try with the spaces and see what happens.
Harbs
On Sep 1, 2013, at 5:41 PM, Alex Harui wrote:
> Use set command to dump environment. Maybe a hidden char in there?
>
>
>
>
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Harbs wrote:
>
>
> Still no go:
>
> Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
>
> check-playerglobal-home:
> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
> [echo] playerglobal.version is 11.1
>
> BUILD FAILED
> /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
> variable PLAYERGLOBAL_HOME is not set to a directory
>
> Total time: 0 seconds
>
> It's been a while since I felt like such an idiot… ;-)
>
> Maybe I'll try to restart my machine a bit later…
>
> On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
>
>> Hi,
>>
>> There's still a space in the path - try removing that? I know it was an
>> issue early on but thought it had been fixed - perhaps not.
>>
>>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>>
>> Thanks,
>> Justin
>>
>>
>
Re: Building the SDK
Use set command to dump environment. Maybe a hidden char in there?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Harbs wrote:
Still no go:
Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
It's been a while since I felt like such an idiot… ;-)
Maybe I'll try to restart my machine a bit later…
On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
> Hi,
>
> There's still a space in the path - try removing that? I know it was an issue
> early on but thought it had been fixed - perhaps not.
>
>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>
> Thanks,
> Justin
>
>
Re: Building the SDK
Still no go:
Buildfile: /Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/FlexSDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
It's been a while since I felt like such an idiot… ;-)
Maybe I'll try to restart my machine a bit later…
On Sep 1, 2013, at 4:27 PM, Justin Mclean wrote:
> Hi,
>
> There's still a space in the path - try removing that? I know it was an issue
> early on but thought it had been fixed - perhaps not.
>
>> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml
>
> Thanks,
> Justin
>
>
Re: Building the SDK
Hi, There's still a space in the path - try removing that? I know it was an issue early on but thought it had been fixed - perhaps not. > /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml Thanks, Justin
Re: Building the SDK
Never mind. I was missing Documents from the path. Removing the space helps,
but it is still not working:
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
Gavriels-MacBook-Air:Flex SDK harbs$ ls $PLAYERGLOBAL_HOME
11.1
Gavriels-MacBook-Air:Flex SDK harbs$ ls $PLAYERGLOBAL_HOME/11.1
playerglobal.swc
On Sep 1, 2013, at 4:08 PM, Harbs wrote:
> Bah. Removing the space did not help:
>
> check-playerglobal-home:
> [echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
> [echo] playerglobal.version is 11.1
>
> BUILD FAILED
> /Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml:168: The environment
> variable PLAYERGLOBAL_HOME is not set to a directory
>
> Total time: 0 seconds
>
> Gavriels-MacBook-Air:Flex SDK harbs$ echo $PLAYERGLOBAL_HOME
> /Users/harbs/ApacheFlex/Dependencies/player/
>
> I have other work I need to do. I'll come back to this later…
>
> On Sep 1, 2013, at 4:00 PM, Justin Mclean wrote:
>
>> Hi,
>>
>> Your structure looks fine, double check the env variable are full paths not
>> relative, otherwise it may be that there's still an issue with spaces in
>> paths in the build files.
>>
>> Justin
>
Re: Building the SDK
Bah. Removing the space did not help:
check-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/ApacheFlex/git/Flex SDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
Total time: 0 seconds
Gavriels-MacBook-Air:Flex SDK harbs$ echo $PLAYERGLOBAL_HOME
/Users/harbs/ApacheFlex/Dependencies/player/
I have other work I need to do. I'll come back to this later…
On Sep 1, 2013, at 4:00 PM, Justin Mclean wrote:
> Hi,
>
> Your structure looks fine, double check the env variable are full paths not
> relative, otherwise it may be that there's still an issue with spaces in
> paths in the build files.
>
> Justin
Re: Building the SDK
Nope. Escaping the paths does not help. (The variable cannot be set at all.) I guess I'll remove the space in the paths… On Sep 1, 2013, at 4:00 PM, Harbs wrote: > Okay. Getting somewhere… > > It looks like it's splitting the space into two separate paths: > ls: /Users/harbs/Apache: No such file or directory > ls: Flex/Dependencies/player/: No such file or directory > > Does the build script not support vars with spaces? Do I need to double > escape the variable? > > I'm setting it like this: > PLAYERGLOBAL_HOME=/Users/harbs/Apache\ Flex/Dependencies/player/ > > I'll try to double escape the spaces and see if that helps… > > On Sep 1, 2013, at 3:54 PM, Justin Mclean wrote: > >> Hi, >> >>> The variable is set: >>> echo $PLAYERGLOBAL_HOME >>> /Users/harbs/Apache Flex/Dependencies/player/ >>> >>> And the file structure looks like this: >>> /Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc >>> (I only added 11.1) >> >> Looks OK to me but try this: >> ls $PLAYERGLOBAL_HOME >> >> I get: >> 10.0 10.110.210.311.011.111.211.311.411.5 >> 11.611.711.8 >> >> And in each directory is a playerglobal.swc. eg >> ls $PLAYERGLOBAL_HOME/11.5 >> gives: >> playerglobal.swc >> >> You might want to check frameworks/flex-config.xml and see what that >> target-player is set to 11.1 like so " 11.1". >> >> Justin >> >
Re: Building the SDK
Okay. Getting somewhere… It looks like it's splitting the space into two separate paths: ls: /Users/harbs/Apache: No such file or directory ls: Flex/Dependencies/player/: No such file or directory Does the build script not support vars with spaces? Do I need to double escape the variable? I'm setting it like this: PLAYERGLOBAL_HOME=/Users/harbs/Apache\ Flex/Dependencies/player/ I'll try to double escape the spaces and see if that helps… On Sep 1, 2013, at 3:54 PM, Justin Mclean wrote: > Hi, > >> The variable is set: >> echo $PLAYERGLOBAL_HOME >> /Users/harbs/Apache Flex/Dependencies/player/ >> >> And the file structure looks like this: >> /Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc >> (I only added 11.1) > > Looks OK to me but try this: > ls $PLAYERGLOBAL_HOME > > I get: > 10.0 10.110.210.311.011.111.211.311.411.5 > 11.611.711.8 > > And in each directory is a playerglobal.swc. eg > ls $PLAYERGLOBAL_HOME/11.5 > gives: > playerglobal.swc > > You might want to check frameworks/flex-config.xml and see what that > target-player is set to 11.1 like so " 11.1". > > Justin >
Re: Building the SDK
Hi, Your structure looks fine, double check the env variable are full paths not relative, otherwise it may be that there's still an issue with spaces in paths in the build files. Justin
Re: Building the SDK
Hi, > The variable is set: > echo $PLAYERGLOBAL_HOME > /Users/harbs/Apache Flex/Dependencies/player/ > > And the file structure looks like this: > /Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc > (I only added 11.1) Looks OK to me but try this: ls $PLAYERGLOBAL_HOME I get: 10.010.110.210.311.011.111.211.311.411.5 11.611.711.8 And in each directory is a playerglobal.swc. eg ls $PLAYERGLOBAL_HOME/11.5 gives: playerglobal.swc You might want to check frameworks/flex-config.xml and see what that target-player is set to 11.1 like so " 11.1". Justin
Re: Building the SDK
I'm really not having a lot of luck today… I tried building TLF separately just to see what happens and it seems to be looking for "flex-sdk" one level up from TLF: Buildfile: /Users/harbs/Documents/Apache Flex/git/TLF/build.xml [echo] FLEX_HOME is /Users/harbs/Documents/Apache Flex/git/TLF/../flex-sdk BUILD FAILED /Users/harbs/Documents/Apache Flex/git/TLF/build.xml:65: /Users/harbs/Documents/Apache Flex/git/flex-sdk does not exist. My structure looks like this: Documents Apache Flex git Flex SDK (the full sdk repro) TLF Is this wrong? On Sep 1, 2013, at 2:50 PM, Justin Mclean wrote: > Hi, > >> It's been a while since I tried to build the SDK from source and I don't >> remember the details. > > Just follow the README, basically check out the sdk and tlf repos and then > set up the required environment vars and do an "ant main". > > Example environment vars on OSX > ANT_HOME=/usr/share/ant > AIR_HOME=/Users/justinmclean/Documents/air/mac/AdobeAIRSDK/ > PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ > PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel > Bender Toolkit 2/ > TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ > > May also need this if doing a full release. > ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe > Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 > > Hope that helps, > Justin >
Re: Building the SDK
I'm getting this error:
heck-playerglobal-home:
[echo] PLAYERGLOBAL_HOME is ${env.PLAYERGLOBAL_HOME}
[echo] playerglobal.version is 11.1
BUILD FAILED
/Users/harbs/Documents/Apache Flex/git/Flex SDK/build.xml:168: The environment
variable PLAYERGLOBAL_HOME is not set to a directory
The variable is set:
echo $PLAYERGLOBAL_HOME
/Users/harbs/Apache Flex/Dependencies/player/
And the file structure looks like this:
/Users/harbs/Apache Flex/Dependencies/player/11.1/playerglobal.swc
(I only added 11.1)
Any suggestions on what I'm doing wrong?
On Sep 1, 2013, at 3:03 PM, Justin Mclean wrote:
> Hi,
>
> BTW building the SDK and even making it a usable SDK leaves git reasonably
> clean. That way you don't always need to do a full build but just build the
> project you need (taking under a minute compared to 7-8 minutes for a full
> build).
>
> Thanks,
> Justin
Re: Building the SDK
Ah. The readme… :-X Thanks for the list of envoronment vars. That was helpful. Thanks! Harbs On Sep 1, 2013, at 2:50 PM, Justin Mclean wrote: > Hi, > >> It's been a while since I tried to build the SDK from source and I don't >> remember the details. > > Just follow the README, basically check out the sdk and tlf repos and then > set up the required environment vars and do an "ant main". > > Example environment vars on OSX > ANT_HOME=/usr/share/ant > AIR_HOME=/Users/justinmclean/Documents/air/mac/AdobeAIRSDK/ > PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ > PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel > Bender Toolkit 2/ > TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ > > May also need this if doing a full release. > ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe > Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 > > Hope that helps, > Justin >
Re: Building the SDK
Hi, BTW building the SDK and even making it a usable SDK leaves git reasonably clean. That way you don't always need to do a full build but just build the project you need (taking under a minute compared to 7-8 minutes for a full build). Thanks, Justin
Re: Building the SDK
Hi, > It's been a while since I tried to build the SDK from source and I don't > remember the details. Just follow the README, basically check out the sdk and tlf repos and then set up the required environment vars and do an "ant main". Example environment vars on OSX ANT_HOME=/usr/share/ant AIR_HOME=/Users/justinmclean/Documents/air/mac/AdobeAIRSDK/ PLAYERGLOBAL_HOME=/Users/justinmclean/Documents/player/ PIXELBENDER_HOME=/Applications/Utilities/Adobe Utilities-CS5.localized/Pixel Bender Toolkit 2/ TLF_HOME=/Users/justinmclean/Documents/ApacheFlexTLFGit/ May also need this if doing a full release. ADOBE_EXTENSION_MANAGER=/Applications/Adobe Extension Manager CS5/Adobe Extension Manager CS5.app/Contents/MacOS/Adobe Extension Manager CS5 Hope that helps, Justin
Re: Building the SDK
I run such a different setup then the majority here, not sure how much config I can give... but as for keeping your Git Repositories clean, I use one way file syncing. Meaning I sync the files from Git to my SDK build folder. The only downside is having to rebuild the SDK (6-7 mins) after you do that. It does keep your environment clean though. -Mark On Sun, Sep 1, 2013 at 6:29 AM, Harbs wrote: > It's been a while since I tried to build the SDK from source and I don't > remember the details. > > Assuming I have the git repository on my machine, what's the recommended > process for building the SDK while retaining the ability to debug the > source? (without messing up the git directories…) > > I tried looking around the wiki, but did not see instructions (sorry if I > missed it). Any pointers would be very much appreciated! > > Harbs
