Using Eclipse project definitions to build the Flex SDK

If you go to the framework project’s properties, there is a section called Flex Library Compiler, you want to use a specific flex sdk (add a new sdk which points to the trunk, and use that) — you are probably building /against/ the wrong sdk, right code, wrong compiler.



- Jono

---

From: Ben Clinkinbeard <member@adobeforums.com>

Reply-To: <flexsdk-dev@adobeforums.com>

Date: Thu, 3 Apr 2008 12:56:01 -0700

To: <flexsdk-dev@adobeforums.com>

Subject: Re: Using Eclipse project definitions to build the Flex SDK



A new message was posted by Ben Clinkinbeard in



Developers --

  Using Eclipse project definitions to build the Flex SDK



Sorry, I'm not following. My SDK project is from the trunk.



Thanks,

Ben





On Thu, Apr 3, 2008 at 3:32 PM, Jono Spiro <member@adobeforums.com> wrote:

A new message was posted by Jono Spiro in



Developers --

  Using Eclipse project definitions to build the Flex SDK



Try changing the sdk for the framework lib project to trunk (you'll need to add a new flex sdk, name it whatever you want) -- it's in the project properties. It's using the wrong compiler.

- Jono

---

From: Ben Clinkinbeard <member@adobeforums.com>

Reply-To: <flexsdk-dev@adobeforums.com>

Date: Thu, 3 Apr 2008 05:13:43 -0700

To: <flexsdk-dev@adobeforums.com>

Subject: Re: Using Eclipse project definitions to build the Flex SDK



A new message was posted by Ben Clinkinbeard in



Developers --

  Using Eclipse project definitions to build the Flex SDK



I am running FB on top of Eclipse 3.3.2. <http://3.3.2.>  < <http://3.3.2.> http://3.3.2.>  I checked out the whole SDK trunk and can build the main ant task with no errors. I used the instructions mentioned above to create a Flex framework library project and thats where the error comes in. (I had tried to manually build a framework project a few times and it was a nightmare.) I would probably prefer to work on the 3.0.x branch/tag as I hope to submit a patch or two but saw Joe mention that the project defs only existed in the trunk.



Searching Google for the oem error turns up lots of links about projects that had assets deleted and the build got confused but following the instructions on how to fix proved unsuccessful.



Thanks,

Ben







On Thu, Apr 3, 2008 at 1:45 AM, Jono Spiro <member@adobeforums.com> wrote:

A new message was posted by Jono Spiro in



Developers --

  Using Eclipse project definitions to build the Flex SDK



I always forget what that error means when it comes up -- though it's been ages since I've seen it last, literally.



Joe: Since you mention Java 1.5, I'm guessing the errors are in the asdoc package? Those should be turned off (read: turned into a warning) -- Eclipse is a little too persnickety about that particular error. There's a preference for this in the Java section under warnings and errors. It's turned off in the trunk dev projects. Otherwise, you should be able to run the compiler directly with no problems (okay, one more caveat: there's a class loader issue with the OEM, fixed in trunk if you look for my Java 1.5 checkin).



Ben: What is your setup? What are you building (Ryan mentions trunk, Joe mentions 30x), which Eclipse, which dev projects, did you build the sdk from the commandline first, etc.?



Cheers,

Jono

---

View/reply at Using Eclipse project definitions to build the Flex SDK < <http://www.adobeforums.com/webx?13@@.59b4a9d4/3> http://www.adobeforums.com/webx?13@@.59b4a9d4/3>

Replies by email are OK.

Use the unsubscribe < <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3> http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>  form to cancel your email subscription.

---

View/reply at Using Eclipse project definitions to build the Flex SDK < <http://www.adobeforums.com/webx?13@@.59b4a9d4/5> http://www.adobeforums.com/webx?13@@.59b4a9d4/5>

Replies by email are OK.

Use the unsubscribe < <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3> http://www.adobeforums.com/webx?280@@.59b4a9d4!folder=.3c060fa3 <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3> >  form to cancel your email subscription.

---

View/reply at Using Eclipse project definitions to build the Flex SDK <http://www.adobeforums.com/webx?13@@.59b4a9d4/6>

Replies by email are OK.

Use the unsubscribe <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>  form to cancel your email subscription.

---

View/reply at Using Eclipse project definitions to build the Flex SDK <http://www.adobeforums.com/webx?13@@.59b4a9d4/7>

Replies by email are OK.

Use the unsubscribe <http://www.adobeforums.com/webx?280@@.59b4a9d4!folder=.3c060fa3>  form to cancel your email subscription.

Sorry, I'm not following. My SDK project is from the trunk.

Thanks,
Ben

Try changing the sdk for the framework lib project to trunk (you’ll need to add a new flex sdk, name it whatever you want) -- it’s in the project properties. It’s using the wrong compiler.

- Jono

---

From: Ben Clinkinbeard <member@adobeforums.com>

Reply-To: <flexsdk-dev@adobeforums.com>

Date: Thu, 3 Apr 2008 05:13:43 -0700

To: <flexsdk-dev@adobeforums.com>

Subject: Re: Using Eclipse project definitions to build the Flex SDK



A new message was posted by Ben Clinkinbeard in



Developers --

  Using Eclipse project definitions to build the Flex SDK



I am running FB on top of Eclipse 3.3.2. <http://3.3.2.>  I checked out the whole SDK trunk and can build the main ant task with no errors. I used the instructions mentioned above to create a Flex framework library project and thats where the error comes in. (I had tried to manually build a framework project a few times and it was a nightmare.) I would probably prefer to work on the 3.0.x branch/tag as I hope to submit a patch or two but saw Joe mention that the project defs only existed in the trunk.



Searching Google for the oem error turns up lots of links about projects that had assets deleted and the build got confused but following the instructions on how to fix proved unsuccessful.



Thanks,

Ben







On Thu, Apr 3, 2008 at 1:45 AM, Jono Spiro <member@adobeforums.com> wrote:

A new message was posted by Jono Spiro in



Developers --

  Using Eclipse project definitions to build the Flex SDK



I always forget what that error means when it comes up -- though it's been ages since I've seen it last, literally.



Joe: Since you mention Java 1.5, I'm guessing the errors are in the asdoc package? Those should be turned off (read: turned into a warning) -- Eclipse is a little too persnickety about that particular error. There's a preference for this in the Java section under warnings and errors. It's turned off in the trunk dev projects. Otherwise, you should be able to run the compiler directly with no problems (okay, one more caveat: there's a class loader issue with the OEM, fixed in trunk if you look for my Java 1.5 checkin).



Ben: What is your setup? What are you building (Ryan mentions trunk, Joe mentions 30x), which Eclipse, which dev projects, did you build the sdk from the commandline first, etc.?



Cheers,

Jono

---

View/reply at Using Eclipse project definitions to build the Flex SDK <http://www.adobeforums.com/webx?13@@.59b4a9d4/3>

Replies by email are OK.

Use the unsubscribe <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>  form to cancel your email subscription.

---

View/reply at Using Eclipse project definitions to build the Flex SDK <http://www.adobeforums.com/webx?13@@.59b4a9d4/5>

Replies by email are OK.

Use the unsubscribe <http://www.adobeforums.com/webx?280@@.59b4a9d4!folder=.3c060fa3>  form to cancel your email subscription.

I am running FB on top of Eclipse 3.3.2. I checked out the whole SDK trunk and can build the main ant task with no errors. I used the instructions mentioned above to create a Flex framework library project and thats where the error comes in. (I had tried to manually build a framework project a few times and it was a nightmare.) I would probably prefer to work on the 3.0.x branch/tag as I hope to submit a patch or two but saw Joe mention that the project defs only existed in the trunk.


Searching Google for the oem error turns up lots of links about projects that had assets deleted and the build got confused but following the instructions on how to fix proved unsuccessful.

Thanks,
Ben

At this point I do not even attempt to build the Java-based parts of<br />the SDK from Eclipse, it's just way too problematic. I only use the<br />project defs to browse the source and to work in the debugger, I do<br />the builds entirely with ant.<br /><br /><br />On Thu, Apr 3, 2008 at 1:45 AM, Jono Spiro <member@adobeforums.com> wrote:<br />> A new message was posted by Jono Spiro in<br />><br />> Developers --<br />> Using Eclipse project definitions to build the Flex SDK<br />><br />> I always forget what that error means when it comes up -- though it's been<br />> ages since I've seen it last, literally.<br />><br />> Joe: Since you mention Java 1.5, I'm guessing the errors are in the asdoc<br />> package? Those should be turned off (read: turned into a warning) -- Eclipse<br />> is a little too persnickety about that particular error. There's a<br />> preference for this in the Java section under warnings and errors. It's<br />> turned off in the trunk dev projects. Otherwise, you should be able to run<br />> the compiler directly with no problems (okay, one more caveat: there's a<br />> class loader issue with the OEM, fixed in trunk if you look for my Java 1.5<br />> checkin).<br />><br />> Ben: What is your setup? What are you building (Ryan mentions trunk, Joe<br />> mentions 30x), which Eclipse, which dev projects, did you build the sdk from<br />> the commandline first, etc.?<br />><br />> Cheers,<br />> Jono<br />><br />><br />> ________________________________<br />> View/reply at Using Eclipse project definitions to build the Flex SDK<br />> Replies by email are OK.<br />> Use the unsubscribe form to cancel your email subscription.<br />><br />><br /><br /><br /><br />-- <br />... . . . j

I always forget what that error means when it comes up -- though it's been ages since I've seen it last, literally.

Joe: Since you mention Java 1.5, I'm guessing the errors are in the asdoc package? Those should be turned off (read: turned into a warning) -- Eclipse is a little too persnickety about that particular error. There's a preference for this in the Java section under warnings and errors. It's turned off in the trunk dev projects. Otherwise, you should be able to run the compiler directly with no problems (okay, one more caveat: there's a class loader issue with the OEM, fixed in trunk if you look for my Java 1.5 checkin).

Ben: What is your setup? What are you building (Ryan mentions trunk, Joe mentions 30x), which Eclipse, which dev projects, did you build the sdk from the commandline first, etc.?

Cheers,
Jono

I followed the instructions in the readme but am now getting the 'unable to export SWC oem' error.

Thanks,
Ben

Thanks -- I am working with the 3.0.x branch, where these files do not exist, but I think the trunk versions should work OK.

I did eventually succeed yesterday in getting the 3.0.x Eclipse project definitions to work by moving them over and changing them to work with J2SE1.5, but I find that there are still some residual compile errors under Eclipse. Doesn't matter too much, since I'm using Eclipse to browse and run the debugger, not to build.

The project definitions should exist in: trunk\development\eclipse\flex

There's a readme.txt in trunk\development\eclipse

Let me know if that works for you (or if you can't find it).

-Ryan