Re: Cross Development (was Re: linking OpenGL)
Re: Cross Development (was Re: linking OpenGL)
- Subject: Re: Cross Development (was Re: linking OpenGL)
- From: Thane Norton <email@hidden>
- Date: Fri, 31 Oct 2003 13:59:12 -0800
Actually, the driver is all C++, with some use of STL. The CPL is a mixed
ObjC++/C++ design. All compiled with gcc 3.3. I don't doubt that they told
you it couldn't be done, but it worked on 5s66. The major changes we had to
deal with was the addition of the wchar stuff. We got around that by
putting this in the pre-compiled header file.
#include <bits/c++config.h>
#undef _GLIBCPP_USE_WCHAR_T
#undef _GLIBCPP_HAVE_MBSTATE_T
#undef _GLIBCPP_HAVE_BTOWC
#undef _GLIBCPP_HAVE_FGETWC
#undef _GLIBCPP_HAVE_FGETWS
#undef _GLIBCPP_HAVE_FPUTWC
#undef _GLIBCPP_HAVE_FPUTWS
#undef _GLIBCPP_HAVE_FWIDE
#undef _GLIBCPP_HAVE_FWPRINTF
#undef _GLIBCPP_HAVE_FWSCANF
#undef _GLIBCPP_HAVE_GETWC
#undef _GLIBCPP_HAVE_GETWCHAR
#undef _GLIBCPP_HAVE_MBRLEN
#undef _GLIBCPP_HAVE_MBRTOWC
#undef _GLIBCPP_HAVE_MBSINIT
#undef _GLIBCPP_HAVE_MBSRTOWCS
#undef _GLIBCPP_HAVE_NL_LANGINFO
#undef _GLIBCPP_HAVE_PUTWC
#undef _GLIBCPP_HAVE_PUTWCHAR
#undef _GLIBCPP_HAVE_STRTOF
#undef _GLIBCPP_HAVE_STRTOLD
#undef _GLIBCPP_HAVE_SWPRINTF
#undef _GLIBCPP_HAVE_SWSCANF
#undef _GLIBCPP_HAVE_UNGETWC
#undef _GLIBCPP_HAVE_VFWPRINTF
#undef _GLIBCPP_HAVE_VFWSCANF
#undef _GLIBCPP_HAVE_VSWPRINTF
#undef _GLIBCPP_HAVE_VSWSCANF
#undef _GLIBCPP_HAVE_VWPRINTF
#undef _GLIBCPP_HAVE_VWSCANF
#undef _GLIBCPP_HAVE_WCRTOMB
#undef _GLIBCPP_HAVE_WCSCAT
#undef _GLIBCPP_HAVE_WCSCHR
#undef _GLIBCPP_HAVE_WCSCMP
#undef _GLIBCPP_HAVE_WCSCOLL
#undef _GLIBCPP_HAVE_WCSCPY
#undef _GLIBCPP_HAVE_WCSCSPN
#undef _GLIBCPP_HAVE_WCSFTIME
#undef _GLIBCPP_HAVE_WCSLEN
#undef _GLIBCPP_HAVE_WCSNCAT
#undef _GLIBCPP_HAVE_WCSNCMP
#undef _GLIBCPP_HAVE_WCSNCPY
#undef _GLIBCPP_HAVE_WCSPBRK
#undef _GLIBCPP_HAVE_WCSRCHR
#undef _GLIBCPP_HAVE_WCSRTOMBS
#undef _GLIBCPP_HAVE_WCSSPN
#undef _GLIBCPP_HAVE_WCSSTR
#undef _GLIBCPP_HAVE_WCSTOD
#undef _GLIBCPP_HAVE_WCSTOF
#undef _GLIBCPP_HAVE_WCSTOK
#undef _GLIBCPP_HAVE_WCSTOL
#undef _GLIBCPP_HAVE_WCSTOUL
#undef _GLIBCPP_HAVE_WCSXFRM
#undef _GLIBCPP_HAVE_WCTOB
#undef _GLIBCPP_HAVE_WMEMCHR
#undef _GLIBCPP_HAVE_WMEMCMP
#undef _GLIBCPP_HAVE_WMEMCPY
#undef _GLIBCPP_HAVE_WMEMMOVE
#undef _GLIBCPP_HAVE_WMEMSET
#undef _GLIBCPP_HAVE_WPRINTF
#undef _GLIBCPP_HAVE_WSCANF
#undef _GLIBCPP_HAVE_WCHAR_H
#undef _GLIBCPP_HAVE_WCTYPE_H
On 10/31/03 1:39 PM, "Thomas Dibble" <email@hidden> wrote:
> I believe your success where others have failed is most likely due to
> language choice. As a driver, I don't imagine you used C++ at all,
> right? The C++ ABI changed completely between gcc 3.1 and gcc 3.3.
> Was your pref pane entirely Obj-C?
>
> Did you use any STL or other C++-specific features? Did you fall back
> to an earlier gcc version (3.1 or 2.95)?
>
> I'm guessing that if you used gcc 3.3 then any gcc-specific headers
> that you included hadn't changed from OSX 10.1 through OSX 10.3.
> Although, I'm a bit curious as to which libgcc.a got linked in for your
> 10.1 project, amongst others.
>
> The last word I had from the compiler team was that 10.1 compatibility
> using gcc 3.3 on C++ code is not possible right now as the gcc 3.3
> ABI-compatible libraries don't exist which are compatible with 10.1.
> You can see this for yourself by examining the usr/include/gcc/ branch
> of the SDK for 10.1: there is no gcc3.3 subtree.
-----------------------------------------
V. Thane Norton III
Macintosh Software Engineer
Wacom Technology Corporation
phone: 360.896.9833 x172
mailto:email@hidden
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.