Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » Intel Mac support status?
Intel Mac support status? [message #176280] Sat, 09 September 2006 17:47 Go to next message
Keath Milligan is currently offline Keath MilliganFriend
Messages: 38
Registered: July 2009
Member
Can anyone comment on the status of Eclipse CDT support for Intel-based
Macs?

Thanks
Re: Intel Mac support status? [message #176333 is a reply to message #176280] Mon, 11 September 2006 11:32 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jamesblackburn+ngnospam.gmail.com

I've used it, it works.

Keath Milligan wrote:
> Can anyone comment on the status of Eclipse CDT support for Intel-based
> Macs?
>
> Thanks
Re: Intel Mac support status? [message #176510 is a reply to message #176333] Wed, 13 September 2006 17:45 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: andrejohn.mas.com.gmail

JB wrote:
>
> I've used it, it works.
>
> Keath Milligan wrote:
>> Can anyone comment on the status of Eclipse CDT support for Intel-based
>> Macs?
>>

Out of curosity I assume Eclipse 3.2 with CDT 3.1?

It should be noted that Eclipse 3.2 is marked as supporting Power PC/Intel
for MacOS X, see:

http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments

CDT is I believe 100% Java.

Andre
Re: Intel Mac support status? [message #176604 is a reply to message #176510] Thu, 14 September 2006 00:50 Go to previous messageGo to next message
Keath Milligan is currently offline Keath MilliganFriend
Messages: 38
Registered: July 2009
Member
Andre-John Mas wrote:
> JB wrote:
>>
>> I've used it, it works.
>>
>> Keath Milligan wrote:
>>> Can anyone comment on the status of Eclipse CDT support for
>>> Intel-based Macs?
>>>
>
> Out of curosity I assume Eclipse 3.2 with CDT 3.1?
>
> It should be noted that Eclipse 3.2 is marked as supporting Power
> PC/Intel for MacOS X, see:
>
> http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments
>
>
> CDT is I believe 100% Java.
>
> Andre

Thanks, I'm going to be upgrading my PowerBook soon and I recall reading
a while back that Intel Mac support wasn't ready yet.
Re: Intel Mac support status? [message #177350 is a reply to message #176604] Tue, 26 September 2006 04:47 Go to previous messageGo to next message
Wong Yuen Ho is currently offline Wong Yuen HoFriend
Messages: 11
Registered: July 2009
Junior Member
I've tried CDT on a Mactel, it doesn't work, and CDT 3.1 doesn't support
the mac/intel architecture yet as far as I know. You can actually see
that only the Mac/PPC architecture is supported from their download page.

CDT most certainly can't be 100% Java. CDT can't possibly be able to
communicate with the native debugger using pure Java.

Yuen-Ho Wong


Keath Milligan wrote:
> Andre-John Mas wrote:
>> JB wrote:
>>>
>>> I've used it, it works.
>>>
>>> Keath Milligan wrote:
>>>> Can anyone comment on the status of Eclipse CDT support for
>>>> Intel-based Macs?
>>>>
>>
>> Out of curosity I assume Eclipse 3.2 with CDT 3.1?
>>
>> It should be noted that Eclipse 3.2 is marked as supporting Power
>> PC/Intel for MacOS X, see:
>>
>> http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments
>>
>>
>> CDT is I believe 100% Java.
>>
>> Andre
>
> Thanks, I'm going to be upgrading my PowerBook soon and I recall reading
> a while back that Intel Mac support wasn't ready yet.
Re: Intel Mac support status? [message #178245 is a reply to message #177350] Thu, 12 October 2006 03:45 Go to previous messageGo to next message
Mike Jackson is currently offline Mike JacksonFriend
Messages: 23
Registered: July 2009
Junior Member
On 2006-09-26 00:47:11 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:

> I've tried CDT on a Mactel, it doesn't work, and CDT 3.1 doesn't
> support the mac/intel architecture yet as far as I know. You can
> actually see that only the Mac/PPC architecture is supported from their
> download page.
>
> CDT most certainly can't be 100% Java. CDT can't possibly be able to
> communicate with the native debugger using pure Java.
>
> Yuen-Ho Wong
>
>
> Keath Milligan wrote:
>> Andre-John Mas wrote:
>>> JB wrote:
>>>>
>>>> I've used it, it works.
>>>>
>>>> Keath Milligan wrote:
>>>>> Can anyone comment on the status of Eclipse CDT support for Intel-based Macs?
>>>>>
>>>
>>> Out of curosity I assume Eclipse 3.2 with CDT 3.1?
>>>
>>> It should be noted that Eclipse 3.2 is marked as supporting Power
>>> PC/Intel for MacOS X, see:
>>>
>>> http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments

CDT
>>>
>>> is I believe 100% Java.
>>>
>>> Andre
>>
>> Thanks, I'm going to be upgrading my PowerBook soon and I recall
>> reading a while back that Intel Mac support wasn't ready yet.

Eclipse 3.2.x is Universal Binary. I was just exploring the CDT
distribution (3.1.1 I believe) and sure enough, the small JNI libs are
both PPC. It was easy enough to find the sources, type "make" in a
terminal in the directory and have i386 jni libs produced.

I changed the Makefile to now create Universal Binaries of the jni
libraries. You will need OS X 10.4.8 and Xcode 2.4 to build them.

# makefile for libspawner.so
# See
http://developer.apple.com/documentation/Java/Conceptual/Jav a141Development/Core_APIs/chapter_6_section_4.html

JAVA_HOME

= /Library/Java/Home
ifeq ($(JAVA_HOME),)
$(warning JAVA_HOME not set in environment)
endif

# Defaults which can be overridden.
OS = macosx
ARCH = Universal
SYS_ROOT=/Developer/SDKs/MacOSX10.4u.sdk
JDK_INCLUDES= $(SYS_ROOT)/System/Library/Frameworks/JavaVM.framework/Heade rs

CC=gcc
LD=libtool
CPPFLAGS = -I. -I$(JDK_INCLUDES)
CFLAGS +=-fPIC -D_REENTRANT -O -g \
-isysroot $(SYS_ROOT) -arch i386 -arch ppc
LDFLAGS=-arch ppc -arch i386 -isysroot $(SYS_ROOT)

INSTALL_DIR = ../os/$(OS)/$(ARCH)

LIB_NAME_SPAWNER = libspawner.dylib
LIB_NAME_FULL_SPAWNER = $(INSTALL_DIR)/libspawner.jnilib
OBJS_SPAWNER=spawner.o io.o exec_unix.o exec_pty.o openpty.o pfind.o

LIB_NAME_PTY = libpty.so
LIB_NAME_FULL_PTY = $(INSTALL_DIR)/libpty.jnilib
OBJS_PTY= openpty.o pty.o ptyio.o

OBJS = $(OBJS_SPAWNER) $(OBJS_PTY)

all: $(LIB_NAME_FULL_SPAWNER) $(LIB_NAME_FULL_PTY)

rebuild: clean all

$(LIB_NAME_FULL_SPAWNER) : $(OBJS_SPAWNER)
mkdir -p $(INSTALL_DIR)
$(CC) -dynamiclib -o $(LIB_NAME_FULL_SPAWNER) $(OBJS_SPAWNER) -lc
-framework JavaVM $(LDFLAGS)

$(LIB_NAME_FULL_PTY): $(OBJS_PTY)
mkdir -p $(INSTALL_DIR)
$(CC) -dynamiclib -o $(LIB_NAME_FULL_PTY) $(OBJS_PTY) -lc -framework
JavaVM $(LDFLAGS)

clean :
$(RM) $(OBJS_SPAWNER) $(LIB_NAME_FULL_SPAWNER)
$(RM) $(OBJS_PTY) $(LIB_NAME_FULL_PTY)
Re: Intel Mac support status? [message #178274 is a reply to message #178245] Thu, 12 October 2006 08:05 Go to previous messageGo to next message
Wong Yuen Ho is currently offline Wong Yuen HoFriend
Messages: 11
Registered: July 2009
Junior Member
If this is tested and works as it should, maybe you should file a bug
and contribute this change back to the source.

Thanks dude!

Yuen Ho Wong


Mike Jackson wrote:
> On 2006-09-26 00:47:11 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:
>
>> I've tried CDT on a Mactel, it doesn't work, and CDT 3.1 doesn't
>> support the mac/intel architecture yet as far as I know. You can
>> actually see that only the Mac/PPC architecture is supported from
>> their download page.
>>
>> CDT most certainly can't be 100% Java. CDT can't possibly be able to
>> communicate with the native debugger using pure Java.
>>
>> Yuen-Ho Wong
>>
>>
>> Keath Milligan wrote:
>>> Andre-John Mas wrote:
>>>> JB wrote:
>>>>>
>>>>> I've used it, it works.
>>>>>
>>>>> Keath Milligan wrote:
>>>>>> Can anyone comment on the status of Eclipse CDT support for
>>>>>> Intel-based Macs?
>>>>>>
>>>>
>>>> Out of curosity I assume Eclipse 3.2 with CDT 3.1?
>>>>
>>>> It should be noted that Eclipse 3.2 is marked as supporting Power
>>>> PC/Intel for MacOS X, see:
>>>>
>>>> http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments
>>>>
>
> CDT
>>>>
>>>> is I believe 100% Java.
>>>>
>>>> Andre
>>>
>>> Thanks, I'm going to be upgrading my PowerBook soon and I recall
>>> reading a while back that Intel Mac support wasn't ready yet.
>
> Eclipse 3.2.x is Universal Binary. I was just exploring the CDT
> distribution (3.1.1 I believe) and sure enough, the small JNI libs are
> both PPC. It was easy enough to find the sources, type "make" in a
> terminal in the directory and have i386 jni libs produced.
>
> I changed the Makefile to now create Universal Binaries of the jni
> libraries. You will need OS X 10.4.8 and Xcode 2.4 to build them.
>
> # makefile for libspawner.so
> # See
> http://developer.apple.com/documentation/Java/Conceptual/Jav a141Development/Core_APIs/chapter_6_section_4.html
>
>
> JAVA_HOME
> = /Library/Java/Home
> ifeq ($(JAVA_HOME),)
> $(warning JAVA_HOME not set in environment)
> endif
>
> # Defaults which can be overridden.
> OS = macosx
> ARCH = Universal
> SYS_ROOT=/Developer/SDKs/MacOSX10.4u.sdk
> JDK_INCLUDES=
> $(SYS_ROOT)/System/Library/Frameworks/JavaVM.framework/Heade rs
>
> CC=gcc
> LD=libtool
> CPPFLAGS = -I. -I$(JDK_INCLUDES)
> CFLAGS +=-fPIC -D_REENTRANT -O -g \
> -isysroot $(SYS_ROOT) -arch i386 -arch ppc
> LDFLAGS=-arch ppc -arch i386 -isysroot $(SYS_ROOT)
>
> INSTALL_DIR = ../os/$(OS)/$(ARCH)
>
> LIB_NAME_SPAWNER = libspawner.dylib
> LIB_NAME_FULL_SPAWNER = $(INSTALL_DIR)/libspawner.jnilib
> OBJS_SPAWNER=spawner.o io.o exec_unix.o exec_pty.o openpty.o pfind.o
>
> LIB_NAME_PTY = libpty.so
> LIB_NAME_FULL_PTY = $(INSTALL_DIR)/libpty.jnilib
> OBJS_PTY= openpty.o pty.o ptyio.o
>
> OBJS = $(OBJS_SPAWNER) $(OBJS_PTY)
>
> all: $(LIB_NAME_FULL_SPAWNER) $(LIB_NAME_FULL_PTY)
>
> rebuild: clean all
>
> $(LIB_NAME_FULL_SPAWNER) : $(OBJS_SPAWNER)
> mkdir -p $(INSTALL_DIR)
> $(CC) -dynamiclib -o $(LIB_NAME_FULL_SPAWNER) $(OBJS_SPAWNER) -lc
> -framework JavaVM $(LDFLAGS)
>
> $(LIB_NAME_FULL_PTY): $(OBJS_PTY)
> mkdir -p $(INSTALL_DIR)
> $(CC) -dynamiclib -o $(LIB_NAME_FULL_PTY) $(OBJS_PTY) -lc -framework
> JavaVM $(LDFLAGS)
>
> clean :
> $(RM) $(OBJS_SPAWNER) $(LIB_NAME_FULL_SPAWNER)
> $(RM) $(OBJS_PTY) $(LIB_NAME_FULL_PTY)
>
>
>
>
>
>
>
>
Re: Intel Mac support status? [message #178314 is a reply to message #178274] Thu, 12 October 2006 12:46 Go to previous messageGo to next message
Mike Jackson is currently offline Mike JacksonFriend
Messages: 23
Registered: July 2009
Junior Member
I tested this on a MacBook Pro and a Powerbook G4 both running OS X
10.4.8 and Xcode 2.4. Both Built a universal Binary library
successfully. However these are the unknowns:

Where do I "install" the jni libraries so that I know they are working
correctly?
Where do I file a bug report? Is that with the Main Eclipse bug tracking site?
Due to the way I built the libs, I may have put a minimal system
requirement of OS X 10.4.x on them.
I Do not know what OS X versions CDT, and for that matter Eclipse
itself, wants to support.
We actually need some others to test this to see if it really does
work. Just because it works on my system doesn't mean it will work
everywhere.

Thanks
Mike Jackson

On 2006-10-12 04:05:59 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:

> If this is tested and works as it should, maybe you should file a bug
> and contribute this change back to the source.
>
> Thanks dude!
>
> Yuen Ho Wong
>
>
> Mike Jackson wrote:
>> On 2006-09-26 00:47:11 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:
>>
>>> I've tried CDT on a Mactel, it doesn't work, and CDT 3.1 doesn't
>>> support the mac/intel architecture yet as far as I know. You can
>>> actually see that only the Mac/PPC architecture is supported from their
>>> download page.
>>>
>>> CDT most certainly can't be 100% Java. CDT can't possibly be able to
>>> communicate with the native debugger using pure Java.
>>>
>>> Yuen-Ho Wong
>>>
>>>
>>> Keath Milligan wrote:
>>>> Andre-John Mas wrote:
>>>>> JB wrote:
>>>>>>
>>>>>> I've used it, it works.
>>>>>>
>>>>>> Keath Milligan wrote:
>>>>>>> Can anyone comment on the status of Eclipse CDT support for Intel-based Macs?
>>>>>>>
>>>>>
>>>>> Out of curosity I assume Eclipse 3.2 with CDT 3.1?
>>>>>
>>>>> It should be noted that Eclipse 3.2 is marked as supporting Power
>>>>> PC/Intel for MacOS X, see:
>>>>>
>>>>> http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments

CDT

is
>>>>>
>>>>> I believe 100% Java.
>>>>>
>>>>> Andre
>>>>
>>>> Thanks, I'm going to be upgrading my PowerBook soon and I recall
>>>> reading a while back that Intel Mac support wasn't ready yet.
>>
>> Eclipse 3.2.x is Universal Binary. I was just exploring the CDT
>> distribution (3.1.1 I believe) and sure enough, the small JNI libs are
>> both PPC. It was easy enough to find the sources, type "make" in a
>> terminal in the directory and have i386 jni libs produced.
>>
>> I changed the Makefile to now create Universal Binaries of the jni
>> libraries. You will need OS X 10.4.8 and Xcode 2.4 to build them.
>>
>> # makefile for libspawner.so
>> # See
>> http://developer.apple.com/documentation/Java/Conceptual/Jav a141Development/Core_APIs/chapter_6_section_4.html

JAVA_HOME
=
>>
>> /Library/Java/Home
>> ifeq ($(JAVA_HOME),)
>> $(warning JAVA_HOME not set in environment)
>> endif
>>
>> # Defaults which can be overridden.
>> OS = macosx
>> ARCH = Universal
>> SYS_ROOT=/Developer/SDKs/MacOSX10.4u.sdk
>> JDK_INCLUDES= $(SYS_ROOT)/System/Library/Frameworks/JavaVM.framework/Heade rs
>>
>> CC=gcc
>> LD=libtool
>> CPPFLAGS = -I. -I$(JDK_INCLUDES)
>> CFLAGS +=-fPIC -D_REENTRANT -O -g \
>> -isysroot $(SYS_ROOT) -arch i386 -arch ppc
>> LDFLAGS=-arch ppc -arch i386 -isysroot $(SYS_ROOT)
>>
>> INSTALL_DIR = ../os/$(OS)/$(ARCH)
>>
>> LIB_NAME_SPAWNER = libspawner.dylib
>> LIB_NAME_FULL_SPAWNER = $(INSTALL_DIR)/libspawner.jnilib
>> OBJS_SPAWNER=spawner.o io.o exec_unix.o exec_pty.o openpty.o pfind.o
>>
>> LIB_NAME_PTY = libpty.so
>> LIB_NAME_FULL_PTY = $(INSTALL_DIR)/libpty.jnilib
>> OBJS_PTY= openpty.o pty.o ptyio.o
>>
>> OBJS = $(OBJS_SPAWNER) $(OBJS_PTY)
>>
>> all: $(LIB_NAME_FULL_SPAWNER) $(LIB_NAME_FULL_PTY)
>>
>> rebuild: clean all
>>
>> $(LIB_NAME_FULL_SPAWNER) : $(OBJS_SPAWNER)
>> mkdir -p $(INSTALL_DIR)
>> $(CC) -dynamiclib -o $(LIB_NAME_FULL_SPAWNER) $(OBJS_SPAWNER) -lc
>> -framework JavaVM $(LDFLAGS)
>>
>> $(LIB_NAME_FULL_PTY): $(OBJS_PTY)
>> mkdir -p $(INSTALL_DIR)
>> $(CC) -dynamiclib -o $(LIB_NAME_FULL_PTY) $(OBJS_PTY) -lc
>> -framework JavaVM $(LDFLAGS)
>>
>> clean :
>> $(RM) $(OBJS_SPAWNER) $(LIB_NAME_FULL_SPAWNER)
>> $(RM) $(OBJS_PTY) $(LIB_NAME_FULL_PTY)
Re: Intel Mac support status? [message #178344 is a reply to message #178314] Thu, 12 October 2006 16:27 Go to previous messageGo to next message
Wong Yuen Ho is currently offline Wong Yuen HoFriend
Messages: 11
Registered: July 2009
Junior Member
Yes you can use the bugzilla on eclipse.org. According to eclipse.org,
Eclipse 3.2 currently only supports OS X 10.4, so I guess that's the
same for CDT. I have idea what to do with the JNI libs, I've never built
them before, if only the CDT Devs will respond... If you file a bug, I'm
sure the CDT team will advise you what to do on Bugzilla, although I'm
fairly certain they'll tell you to run the JUnit test cases that come
with CDT SDK to check for regressions.

Yuen Ho Wong


Mike Jackson wrote:
> I tested this on a MacBook Pro and a Powerbook G4 both running OS X
> 10.4.8 and Xcode 2.4. Both Built a universal Binary library
> successfully. However these are the unknowns:
>
> Where do I "install" the jni libraries so that I know they are working
> correctly?
> Where do I file a bug report? Is that with the Main Eclipse bug tracking
> site?
> Due to the way I built the libs, I may have put a minimal system
> requirement of OS X 10.4.x on them.
> I Do not know what OS X versions CDT, and for that matter Eclipse
> itself, wants to support.
> We actually need some others to test this to see if it really does work.
> Just because it works on my system doesn't mean it will work everywhere.
>
> Thanks
> Mike Jackson
>
> On 2006-10-12 04:05:59 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:
>
>> If this is tested and works as it should, maybe you should file a bug
>> and contribute this change back to the source.
>>
>> Thanks dude!
>>
>> Yuen Ho Wong
>>
>>
>> Mike Jackson wrote:
>>> On 2006-09-26 00:47:11 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:
>>>
>>>> I've tried CDT on a Mactel, it doesn't work, and CDT 3.1 doesn't
>>>> support the mac/intel architecture yet as far as I know. You can
>>>> actually see that only the Mac/PPC architecture is supported from
>>>> their download page.
>>>>
>>>> CDT most certainly can't be 100% Java. CDT can't possibly be able to
>>>> communicate with the native debugger using pure Java.
>>>>
>>>> Yuen-Ho Wong
>>>>
>>>>
>>>> Keath Milligan wrote:
>>>>> Andre-John Mas wrote:
>>>>>> JB wrote:
>>>>>>>
>>>>>>> I've used it, it works.
>>>>>>>
>>>>>>> Keath Milligan wrote:
>>>>>>>> Can anyone comment on the status of Eclipse CDT support for
>>>>>>>> Intel-based Macs?
>>>>>>>>
>>>>>>
>>>>>> Out of curosity I assume Eclipse 3.2 with CDT 3.1?
>>>>>>
>>>>>> It should be noted that Eclipse 3.2 is marked as supporting Power
>>>>>> PC/Intel for MacOS X, see:
>>>>>>
>>>>>> http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments
>>>>>>
>
> CDT
>
> is
>>>>>>
>>>>>> I believe 100% Java.
>>>>>>
>>>>>> Andre
>>>>>
>>>>> Thanks, I'm going to be upgrading my PowerBook soon and I recall
>>>>> reading a while back that Intel Mac support wasn't ready yet.
>>>
>>> Eclipse 3.2.x is Universal Binary. I was just exploring the CDT
>>> distribution (3.1.1 I believe) and sure enough, the small JNI libs
>>> are both PPC. It was easy enough to find the sources, type "make" in
>>> a terminal in the directory and have i386 jni libs produced.
>>>
>>> I changed the Makefile to now create Universal Binaries of the jni
>>> libraries. You will need OS X 10.4.8 and Xcode 2.4 to build them.
>>>
>>> # makefile for libspawner.so
>>> # See
>>> http://developer.apple.com/documentation/Java/Conceptual/Jav a141Development/Core_APIs/chapter_6_section_4.html
>>>
>
> JAVA_HOME
> =
>>>
>>> /Library/Java/Home
>>> ifeq ($(JAVA_HOME),)
>>> $(warning JAVA_HOME not set in environment)
>>> endif
>>>
>>> # Defaults which can be overridden.
>>> OS = macosx
>>> ARCH = Universal
>>> SYS_ROOT=/Developer/SDKs/MacOSX10.4u.sdk
>>> JDK_INCLUDES=
>>> $(SYS_ROOT)/System/Library/Frameworks/JavaVM.framework/Heade rs
>>>
>>> CC=gcc
>>> LD=libtool
>>> CPPFLAGS = -I. -I$(JDK_INCLUDES)
>>> CFLAGS +=-fPIC -D_REENTRANT -O -g \
>>> -isysroot $(SYS_ROOT) -arch i386 -arch ppc
>>> LDFLAGS=-arch ppc -arch i386 -isysroot $(SYS_ROOT)
>>>
>>> INSTALL_DIR = ../os/$(OS)/$(ARCH)
>>>
>>> LIB_NAME_SPAWNER = libspawner.dylib
>>> LIB_NAME_FULL_SPAWNER = $(INSTALL_DIR)/libspawner.jnilib
>>> OBJS_SPAWNER=spawner.o io.o exec_unix.o exec_pty.o openpty.o pfind.o
>>>
>>> LIB_NAME_PTY = libpty.so
>>> LIB_NAME_FULL_PTY = $(INSTALL_DIR)/libpty.jnilib
>>> OBJS_PTY= openpty.o pty.o ptyio.o
>>>
>>> OBJS = $(OBJS_SPAWNER) $(OBJS_PTY)
>>>
>>> all: $(LIB_NAME_FULL_SPAWNER) $(LIB_NAME_FULL_PTY)
>>>
>>> rebuild: clean all
>>>
>>> $(LIB_NAME_FULL_SPAWNER) : $(OBJS_SPAWNER)
>>> mkdir -p $(INSTALL_DIR)
>>> $(CC) -dynamiclib -o $(LIB_NAME_FULL_SPAWNER) $(OBJS_SPAWNER) -lc
>>> -framework JavaVM $(LDFLAGS)
>>>
>>> $(LIB_NAME_FULL_PTY): $(OBJS_PTY)
>>> mkdir -p $(INSTALL_DIR)
>>> $(CC) -dynamiclib -o $(LIB_NAME_FULL_PTY) $(OBJS_PTY) -lc
>>> -framework JavaVM $(LDFLAGS)
>>>
>>> clean :
>>> $(RM) $(OBJS_SPAWNER) $(LIB_NAME_FULL_SPAWNER)
>>> $(RM) $(OBJS_PTY) $(LIB_NAME_FULL_PTY)
>
>
Re: Intel Mac support status? [message #178374 is a reply to message #178344] Fri, 13 October 2006 04:02 Go to previous message
Mike Jackson is currently offline Mike JacksonFriend
Messages: 23
Registered: July 2009
Junior Member
Bug number 160799
has been filed...

Mike Jackson

On 2006-10-12 12:27:16 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:

> Yes you can use the bugzilla on eclipse.org. According to eclipse.org,
> Eclipse 3.2 currently only supports OS X 10.4, so I guess that's the
> same for CDT. I have idea what to do with the JNI libs, I've never
> built them before, if only the CDT Devs will respond... If you file a
> bug, I'm sure the CDT team will advise you what to do on Bugzilla,
> although I'm fairly certain they'll tell you to run the JUnit test
> cases that come with CDT SDK to check for regressions.
>
> Yuen Ho Wong
>
>
> Mike Jackson wrote:
>> I tested this on a MacBook Pro and a Powerbook G4 both running OS X
>> 10.4.8 and Xcode 2.4. Both Built a universal Binary library
>> successfully. However these are the unknowns:
>>
>> Where do I "install" the jni libraries so that I know they are working
>> correctly?
>> Where do I file a bug report? Is that with the Main Eclipse bug tracking site?
>> Due to the way I built the libs, I may have put a minimal system
>> requirement of OS X 10.4.x on them.
>> I Do not know what OS X versions CDT, and for that matter Eclipse
>> itself, wants to support.
>> We actually need some others to test this to see if it really does
>> work. Just because it works on my system doesn't mean it will work
>> everywhere.
>>
>> Thanks
>> Mike Jackson
>>
>> On 2006-10-12 04:05:59 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:
>>
>>> If this is tested and works as it should, maybe you should file a bug
>>> and contribute this change back to the source.
>>>
>>> Thanks dude!
>>>
>>> Yuen Ho Wong
>>>
>>>
>>> Mike Jackson wrote:
>>>> On 2006-09-26 00:47:11 -0400, Yuen Ho Wong <wyuenho@gmail.com> said:
>>>>
>>>>> I've tried CDT on a Mactel, it doesn't work, and CDT 3.1 doesn't
>>>>> support the mac/intel architecture yet as far as I know. You can
>>>>> actually see that only the Mac/PPC architecture is supported from their
>>>>> download page.
>>>>>
>>>>> CDT most certainly can't be 100% Java. CDT can't possibly be able to
>>>>> communicate with the native debugger using pure Java.
>>>>>
>>>>> Yuen-Ho Wong
>>>>>
>>>>>
>>>>> Keath Milligan wrote:
>>>>>> Andre-John Mas wrote:
>>>>>>> JB wrote:
>>>>>>>>
>>>>>>>> I've used it, it works.
>>>>>>>>
>>>>>>>> Keath Milligan wrote:
>>>>>>>>> Can anyone comment on the status of Eclipse CDT support for Intel-based Macs?
>>>>>>>>>
>>>>>>>
>>>>>>> Out of curosity I assume Eclipse 3.2 with CDT 3.1?
>>>>>>>
>>>>>>> It should be noted that Eclipse 3.2 is marked as supporting Power
>>>>>>> PC/Intel for MacOS X, see:
>>>>>>>
>>>>>>> http://www.eclipse.org/eclipse/development/eclipse_project_p lan_3_2.html#TargetOperatingEnvironments

CDT

is

I
>>>>>>>
>>>>>>> believe 100% Java.
>>>>>>>
>>>>>>> Andre
>>>>>>
>>>>>> Thanks, I'm going to be upgrading my PowerBook soon and I recall
>>>>>> reading a while back that Intel Mac support wasn't ready yet.
>>>>
>>>> Eclipse 3.2.x is Universal Binary. I was just exploring the CDT
>>>> distribution (3.1.1 I believe) and sure enough, the small JNI libs are
>>>> both PPC. It was easy enough to find the sources, type "make" in a
>>>> terminal in the directory and have i386 jni libs produced.
>>>>
>>>> I changed the Makefile to now create Universal Binaries of the jni
>>>> libraries. You will need OS X 10.4.8 and Xcode 2.4 to build them.
>>>>
>>>> # makefile for libspawner.so
>>>> # See
>>>> http://developer.apple.com/documentation/Java/Conceptual/Jav a141Development/Core_APIs/chapter_6_section_4.html

JAVA_HOME
=

/Library/Java/Home
ifeq
>>>>
>>>> ($(JAVA_HOME),)
>>>> $(warning JAVA_HOME not set in environment)
>>>> endif
>>>>
>>>> # Defaults which can be overridden.
>>>> OS = macosx
>>>> ARCH = Universal
>>>> SYS_ROOT=/Developer/SDKs/MacOSX10.4u.sdk
>>>> JDK_INCLUDES= $(SYS_ROOT)/System/Library/Frameworks/JavaVM.framework/Heade rs
>>>>
>>>> CC=gcc
>>>> LD=libtool
>>>> CPPFLAGS = -I. -I$(JDK_INCLUDES)
>>>> CFLAGS +=-fPIC -D_REENTRANT -O -g \
>>>> -isysroot $(SYS_ROOT) -arch i386 -arch ppc
>>>> LDFLAGS=-arch ppc -arch i386 -isysroot $(SYS_ROOT)
>>>>
>>>> INSTALL_DIR = ../os/$(OS)/$(ARCH)
>>>>
>>>> LIB_NAME_SPAWNER = libspawner.dylib
>>>> LIB_NAME_FULL_SPAWNER = $(INSTALL_DIR)/libspawner.jnilib
>>>> OBJS_SPAWNER=spawner.o io.o exec_unix.o exec_pty.o openpty.o pfind.o
>>>>
>>>> LIB_NAME_PTY = libpty.so
>>>> LIB_NAME_FULL_PTY = $(INSTALL_DIR)/libpty.jnilib
>>>> OBJS_PTY= openpty.o pty.o ptyio.o
>>>>
>>>> OBJS = $(OBJS_SPAWNER) $(OBJS_PTY)
>>>>
>>>> all: $(LIB_NAME_FULL_SPAWNER) $(LIB_NAME_FULL_PTY)
>>>>
>>>> rebuild: clean all
>>>>
>>>> $(LIB_NAME_FULL_SPAWNER) : $(OBJS_SPAWNER)
>>>> mkdir -p $(INSTALL_DIR)
>>>> $(CC) -dynamiclib -o $(LIB_NAME_FULL_SPAWNER) $(OBJS_SPAWNER) -lc
>>>> -framework JavaVM $(LDFLAGS)
>>>>
>>>> $(LIB_NAME_FULL_PTY): $(OBJS_PTY)
>>>> mkdir -p $(INSTALL_DIR)
>>>> $(CC) -dynamiclib -o $(LIB_NAME_FULL_PTY) $(OBJS_PTY) -lc
>>>> -framework JavaVM $(LDFLAGS)
>>>>
>>>> clean :
>>>> $(RM) $(OBJS_SPAWNER) $(LIB_NAME_FULL_SPAWNER)
>>>> $(RM) $(OBJS_PTY) $(LIB_NAME_FULL_PTY)
Previous Topic:Hover
Next Topic:How to write Java code to Create Make Target
Goto Forum:
  


Current Time: Thu Dec 18 07:30:22 GMT 2014

Powered by FUDForum. Page generated in 0.04195 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software