Hi,
> So is everyone doing it the import projects way, then?
I don't. I import the whole SDK as a general project (under new project) and
just use ant to compile.
Justin
It makes me think it isn’t finding airglobal.swc.
It could be the one you have is corrupted.
HTH,
-Alex
On 12/4/14, 12:24 PM, "Mihai Chira" wrote:
>Ok, I'm giving up for today.
>
>I managed to get makeApacheFlexForIDE.bat running after I commented
>out the copying task. But now that the AIR sd
Ok, I'm giving up for today.
I managed to get makeApacheFlexForIDE.bat running after I commented
out the copying task. But now that the AIR sdk seems to be all right
too, I still get the same error when compiling with IntelliJ.
So is everyone doing it the import projects way, then?
On 4 December
Update: after commenting out the PackageMXP target, the "ant
-Dbuild.number=20141204 -Dbuild.noprompt=release" command worked, but
the compilation fails with the same error: "The definition of base
class Error was not found."
Alex, after that I also did an "ant main", which was successful, but
now
FWIW, The way I work, is by adding textLayout as a library project to FB. I
take care to never actually build it in FB. I always build it using ant. I’ve
found without adding lextLayout to Flash Builder, I cannot use the features
like jumping to code, and the like.
I then add the binary in the
Mihai,
I don’t think you need to run the “release” target. The “main” target
should be sufficient. And thus you shouldn’t need the MXP tools and can
probably take them out of your environment variables.
-Alex
On 12/4/14, 11:23 AM, "Mihai Chira" wrote:
>Update: running ant -Dbuild.number=20
Update: running ant -Dbuild.number=20141204 -Dbuild.noprompt=release
failed at the PackageMXP target in
frameworks\projects\flash-integration\build.xml:159 with this as the
only information:
___
FlashMXP:
[echo] ADOBE_EXTENSION_MANAGER is c:\Program Files
(
Almost all the projects there have the .actionScriptProperties and
.flexLibProperties. So, just importing it as an existing project into FB
will ensure that the correct config files and compiler directives are
added.
Thanks,
Om
On Thu, Dec 4, 2014 at 10:58 AM, OmPrakash Muppirala
wrote:
> Om,
>
> Om, I think I tried that a while ago and got into a lot of trouble
> because those projects in the 'frameworks/projects' folder had so many
> dependencies and custom compilation flags, etc. I'm glad you could get
> it to run, but I'd like to make the current source a working SDK for
> the IDE.
Thanks for the promptitude guys.
Alex, I am working from the repos indeed.
Erik, thanks for the pointer. I'm just running ant
-Dbuild.number=20141204 -Dbuild.noprompt=release, and then following
the next steps; let's see if that helps.
Om, I think I tried that a while ago and got into a lot of t
The best way I know of is to point FB to a version of the SDK created by
the Flex Installer. Then, add flex-sdk\frameworks\projects\ as Flex
library projects in the same workspace. Then, in your test application,
add the library projects as a 'Project dependency'. This way, you can
continue
Mihai, are you working from a source release artifact or from the repos?
While it is informative if you are having trouble following the
instructions to work from a source release, since you are a committer, it
would be best if you are working from the repos as then you can just check
in a fix.
-A
Not really, I'm afraid. I did just rewrite the README to make the
process feel a bit more logical and structured. Have you looked at
that? Or is that what's causing your troubles? In which case I'd be
interested to know which steps led to the issues you see, and how you
solved them.
Thanks,
EdB
I want to make sure that I bug I raised in tlf is reproducible in the
nightly source. I've never tried making the source sdk the current sdk
before, and it's proving much more difficult than I thought. Here's
what I did:
>ant release (in main sdk folder)
after finally figuring out that I need a cf
14 matches
Mail list logo
