[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[platform-swt-dev] Re: Latest (5/5) OS/X build fails. (Andre Weinand)
|
The illustrious Andre Weinand <weinand@xxxxxxx> writes:
Hmmm, I downloaded the latest build and had no problems in building it.
I did not change anything in the build structure since the last drop.
So I don't know what the problem is.
However, someone at WWDC mentioned that he could not build SWT after he had
upgraded to the 2.0 version of Project Builder. Are you sure that you
tried to build
SWT with the 1.1.1 version (the only supported version)?
I would have loved to have done that.
Here's the saga of woe...
1. try to open the projectBuilder document -- PB crashes over and over.
2. realize that I have 1.1.0 and decide to upgrade.
3. download Dec 2001 Dev tools and "upgrade".
4. this silently downgrades me to 1.0.1
5. look for a long time through the apple site.
6. find only the April 2002 beta Dev tools, upgrade to 2.0 beta.
7. then I get the issue I described...
In addition, since Eclipse on MacOS X is not yet ready for primetime,
I don't see an urgent need
for having a version that runs without any additional work. I would
rather like to see people
being able to build SWT for MacOS X themselves. Maybe this could
enable others to help out out in finding the reason for then above
mentioned problem.
This is very logical!
>I also suspect that the changes in the build process which put the
version number in the plugin directory name are going to make this
process even more painful.
glurph, this sounds very yucky.
BUT
=?ISO-8859-1?Q?Bj=F6rn?= Bubbat <bjoern@xxxxxxxxx> writes:
I also had a problem with the April2002 Developer tools. But it's=20
pretty easy to fix:=20
open the Eclipse project
click on the Targets tab
select OS
click on the Files&Build Phases Tab
In the Shell Script Files section replace
javah -classpath "${OBJROOT}/OS.build/JavaClasses/" -force -d .=20
org.eclipse.swt.internal.carbon.OS=20
with
javah -classpath "${OBJROOT}/Eclipse.build/OS.build/JavaClasses/"
-force -d . org.eclipse.swt.internal.carbon.OS
This works at least for me.
It's building "as I speak".
This makes a lot of sense as I did find that missing file
in the directory that you are indicating for the classpath.
But I don't see how it ever worked!
(final note: the build did appear to work, but I need to
do all the class file installation -- bet it will work
though...)
/t
--
http://loopNY.com ......................An "open loop": shows every Saturday!
http://whatGoes.com/submit .......................... submit to the calendar.
