I would like to get Eclipse ECJ as a port. I tried to put together a Portfile, but I am afraid I don't know how to fill in some of the sections. The version that I know of are : - R-3.3.1.1-200710231652 - R-3.3-200706251500 That can be downloaded from http://download.eclipse.org/eclipse/downloads/drops/R-3.3.1.1-200710231652/e... http://archive.eclipse.org/eclipse/downloads/drops/R-3.3-200706251500/ecjsrc... I don't know when a release is moved from the live site to the archive site. I also don't know how long stuff stays on the archive site. Michael
On Jan 18, 2008, at 15:38, Michael Franz wrote:
I would like to get Eclipse ECJ as a port. I tried to put together a Portfile, but I am afraid I don't know how to fill in some of the sections.
The version that I know of are : - R-3.3.1.1-200710231652 - R-3.3-200706251500
That can be downloaded from http://download.eclipse.org/eclipse/downloads/drops/ R-3.3.1.1-200710231652/ecjsrc.zip http://archive.eclipse.org/eclipse/downloads/drops/ R-3.3-200706251500/ecjsrc.zip
I don't know when a release is moved from the live site to the archive site. I also don't know how long stuff stays on the archive site.
Probably the best way to work on this would be for you to file a Port Request ticket in our issue tracker. Attach your in-progress portfile and Cc me on the ticket and I'll have a look at it.
I can do this. I have one question before I do that. I have it downloading and trying to compile, but it cannot find the working directory. I think this is because the source file does not have a subdirectory. Michael On Jan 18, 2008 4:49 PM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Jan 18, 2008, at 15:38, Michael Franz wrote:
I would like to get Eclipse ECJ as a port. I tried to put together a Portfile, but I am afraid I don't know how to fill in some of the sections.
The version that I know of are : - R-3.3.1.1-200710231652 - R-3.3-200706251500
That can be downloaded from http://download.eclipse.org/eclipse/downloads/drops/ R-3.3.1.1-200710231652/ecjsrc.zip http://archive.eclipse.org/eclipse/downloads/drops/ R-3.3-200706251500/ecjsrc.zip
I don't know when a release is moved from the live site to the archive site. I also don't know how long stuff stays on the archive site.
Probably the best way to work on this would be for you to file a Port Request ticket in our issue tracker. Attach your in-progress portfile and Cc me on the ticket and I'll have a look at it.
On Jan 18, 2008, at 21:20, Michael Franz wrote:
On Jan 18, 2008 4:49 PM, Ryan Schmidt wrote:
On Jan 18, 2008, at 15:38, Michael Franz wrote:
I would like to get Eclipse ECJ as a port. I tried to put together a Portfile, but I am afraid I don't know how to fill in some of the sections.
The version that I know of are : - R-3.3.1.1-200710231652 - R-3.3-200706251500
That can be downloaded from http://download.eclipse.org/eclipse/downloads/drops/ R-3.3.1.1-200710231652/ecjsrc.zip http://archive.eclipse.org/eclipse/downloads/drops/ R-3.3-200706251500/ecjsrc.zip
I don't know when a release is moved from the live site to the archive site. I also don't know how long stuff stays on the archive site.
Probably the best way to work on this would be for you to file a Port Request ticket in our issue tracker. Attach your in-progress portfile and Cc me on the ticket and I'll have a look at it.
I can do this. I have one question before I do that. I have it downloading and trying to compile, but it cannot find the working directory. I think this is because the source file does not have a subdirectory.
Maybe you want to use extract.mkdir yes This option was added in MacPorts 1.6.0. http://guide.macports.org/#reference.phases.extract
Maybe you want to use
extract.mkdir yes
This option was added in MacPorts 1.6.0.
http://guide.macports.org/#reference.phases.extract
This worked great.
I have made progress on this. I found older versions, which is important, and been able to compile - mostly. The older versions are important since the 3.3.1.1 requires Java 6 to compile (Java 6 API being used). Kaffe and Tiger do not have Java 6 support also. Although Kaffe is a dependency, I don't think it is actually being used to compile (not that I care). Since the version that I can get to compile does not have a build.xml file, how do I create a patch file for a missing file? I can patch an existing file, but how do I add a missing file? diff -u just tells me the file is missing. Michael
On Jan 19, 2008, at 13:15, Michael Franz wrote:
I have made progress on this. I found older versions, which is important, and been able to compile - mostly.
The older versions are important since the 3.3.1.1 requires Java 6 to compile (Java 6 API being used). Kaffe and Tiger do not have Java 6 support also. Although Kaffe is a dependency, I don't think it is actually being used to compile (not that I care).
Since the version that I can get to compile does not have a build.xml file, how do I create a patch file for a missing file? I can patch an existing file, but how do I add a missing file? diff - u just tells me the file is missing.
You can create a patch which creates a file out of thin air. But it's probably more straightforward to just put the file in the port's "files" directory and copy it from there to the right place in the post-patch phase, for example: post-patch { copy ${filespath}/build.xml ${worksrcpath} }
On Jan 19, 2008 7:32 PM, Ryan Schmidt <ryandesign@macports.org> wrote:
On Jan 19, 2008, at 13:15, Michael Franz wrote:
I have made progress on this. I found older versions, which is important, and been able to compile - mostly.
The older versions are important since the 3.3.1.1 requires Java 6 to compile (Java 6 API being used). Kaffe and Tiger do not have Java 6 support also. Although Kaffe is a dependency, I don't think it is actually being used to compile (not that I care).
Since the version that I can get to compile does not have a build.xml file, how do I create a patch file for a missing file? I can patch an existing file, but how do I add a missing file? diff - u just tells me the file is missing.
You can create a patch which creates a file out of thin air. But it's probably more straightforward to just put the file in the port's "files" directory and copy it from there to the right place in the post-patch phase, for example:
post-patch { copy ${filespath}/build.xml ${worksrcpath} }
I'll give this a try.
participants (2)
-
Michael Franz
-
Ryan Schmidt