IMO, if you do add it to the Installer, please make sure it isn't in the main workflow. I don't think too many people are going to do this.
I would argue that if you are planning to make a habit of modifying the SDK, that you get comfortable using Ant scripts. We'll want you to have run 'ant main checkintests' and maybe some mustella tests before submitting your patch. And then, if you are going to use Ant, I think you can use installer.xml to convert the repo into an IDE compatible SDK. Essentially, that Ant script starts after the expansion of the binary package which is pretty close to what you want. And if that doesn't work, I'd be interested in what it takes to get it to work. I think you should run ant main in the repo first to get the compiled binaries, then ant -f installer.xml FWIW, the downside to making the repo into an IDE-compatible SDK, regardless of how you do it, is that you've mixed in a lot more non-Apache code so you have to be careful about the content of your patches and checkins. However, it is way easier to do most changes in an IDE compatible SDK and I'd guess many folks are doing it that way. And also, FWIW, it might just be easier to use a monkey-patch workflow on a released SDK, then merge the changed files into the repo and run the ant scripts. On 3/28/14 3:23 PM, "jude" <flexcapaci...@gmail.com> wrote: >I've read through the manual install steps for installing and building the >SDK and I think I might try to update the installer to add support for >this >(unless someone else wants to). My plan is to let the user select the >directory where Flex has been downloaded or installed already and then >step >through the installer normally. When the install process gets to the part >where it needs to download the SDK it would skip this part and use the >selected directory instead. Let me know if there are any downside to this >approach. > > >On Fri, Mar 28, 2014 at 12:54 PM, jude <flexcapaci...@gmail.com> wrote: > >> I want to work on the Flex SDK and I've cloned the repository down to my >> computer. From what I've gathered so far, cloning the SDK locally does >>not >> install all the necessary components needed to run / compile a Flex >> application, correct? The instructions how to setup the SDK are in the >> readme in the root directory. These say there is a build script in the >>same >> directory to automate all or some of these steps? After I run that is >>that >> all I need to do to work on the SDK? I mean I would still have to point >>FB >> to the Flex SDK path and add Flex SDK and TLF SDK as libraries? >> >> If there are more steps or if you think it's a good idea would it be >> possible to get the Flex installer to point to a local Flex SDK >>repository >> (already downloaded like I have) and set it up for the developer? >>
