Code::Blocks Forums

User forums => General (but related to Code::Blocks) => Topic started by: per_eckerdal on July 10, 2005, 09:00:58 pm

Title: Mac?
Post by: per_eckerdal on July 10, 2005, 09:00:58 pm

Hi!
Just a question out of curiousity: I was just wondering how much is needed for a mac port? Mac OS X is my preferred OS, so support would be pretty neat..

(This post DOES NOT imply that I'm going to code a port, there is a possibility, but don't count on it ;) And i dunno if you even WANT one.. hehe)
/Per Eckerdal

Title: Mac?
Post by: David Perfors on July 10, 2005, 09:16:23 pm

Probably some code has to be changed, but I don't know what.

I am not able to do it, because I don't have a mac :)

Title: Mac?
Post by: per_eckerdal on July 10, 2005, 11:34:47 pm

hehe :)

Title: Mac?
Post by: per_eckerdal on July 10, 2005, 11:36:31 pm

(what I wondered was mostly if you used any library that does not exist for mac..)
/Per Eckerdal

Title: Mac?
Post by: David Perfors on July 10, 2005, 11:46:38 pm

I can't think of one, TinyXML is compiled by us, wxwidgets is still available, I thought that was all...

Title: Mac?
Post by: mandrav on July 11, 2005, 12:28:43 am

The most important goal of C::B is portability across platforms. Because of this, external dependencies are kept to a minimum.
To build C::B you need wxWidgets, STC (in wxWidgets contrib) and TinyXML (included).
I don't own a Mac to try it but I guess that it would build succesfully as it is now. I mean, if wxWidgets is available for Mac, I see no reason for C::B to fail compiling there.

Yiannis.

Title: Mac?
Post by: per_eckerdal on July 11, 2005, 08:42:53 am

(Sorry to disappoint you but, :roll:)
I don't think it will work. OS X 10.4 (the latest version) uses GCC 4 and it is very picky with casts. If you haven't tested with that compiler it will probably not compile.. Most projects aren't very hard to port, tho.
/Per Eckerdal

Title: Mac?
Post by: mandrav on July 11, 2005, 09:31:52 am

Quote

Most projects aren't very hard to port, tho.

That's what 's important. The point is that it will require minor modifications to work, or so I 'm told...

Yiannis.

Title: Mac?
Post by: Profic on July 11, 2005, 09:32:12 am

AFAIR Scintilla itself didn't have port to mac...

Title: Mac?
Post by: mandrav on July 11, 2005, 09:58:38 am

Quote from: Profic

AFAIR Scintilla itself didn't have port to mac...

It seems you remember wrong (http://www.scintilla.org/ScintillaHistory.html).
Search in that link for Mac support.

Yiannis.

PS: I 've never worked with a Mac. Everything I say about it, comes from what I read...

Title: Mac?
Post by: per_eckerdal on July 11, 2005, 10:18:09 am

@mandrav:
My impression of Mac is that it is a relatively stable platform, though not even close to the maturity of linux or windows. The reason I use mac is mac mini, because I need to move my computer around and can't afford a laptop..

MB I should install Gentoo PPC.. (Gentoo rocks.. :))
/Per Eckerdal

Title: Mac?
Post by: per_eckerdal on July 11, 2005, 10:32:12 am

.. and it is severely lacking a good ide :)..

Title: Mac?
Post by: per_eckerdal on July 11, 2005, 11:25:11 am

Now I'm trying to compile Code::Blocks (CVS HEAD, wxWidgets 2.6.1 non-unicode)
There are very many wxChar* <=> char* cast errors. Should I just do (wxChar*), or should I use _() _T(). (I read your discussion about unicode..)
/Per Eckerdal

Title: Mac?
Post by: mandrav on July 11, 2005, 11:53:10 am

Quote from: per_eckerdal

Now I'm trying to compile Code::Blocks (CVS HEAD, wxWidgets 2.6.1 non-unicode)
There are very many wxChar* <=> char* cast errors. Should I just do (wxChar*), or should I use _() _T(). (I read your discussion about unicode..)
/Per Eckerdal

If it fixes the errors, use _() for translatable text and _T() for not translatable (like config options etc).
Then submit a patch ;)

Yiannis.

Title: Mac?
Post by: per_eckerdal on July 11, 2005, 12:04:38 pm

can the _( macro be used for other non-""'s also, e.g. _(fname.GetPath())?
Or should normal casts be used?

EDIT: The answer is no, the _() macro just adds a L to the beginning L"string" for unicode

Title: Mac?
Post by: Profic on July 11, 2005, 01:11:34 pm

Quote

It seems you remember wrong.
Search in that link for Mac support.

Found only one record for "Mac"
First of all I mean native port. AFAIR (again :)) with currrent Mac OS X's BSD background it is possible to build almost any unix application :)

PS. I've worked with mac long ago then MacOS 8.0 was the last, so all I say is from my reading too :)

Title: Mac?
Post by: mandrav on July 11, 2005, 01:26:46 pm

Anyway, Per is trying to build it now so I guess we 're gonna know pretty soon how it goes :)

Yiannis.

Title: Mac?
Post by: per_eckerdal on July 11, 2005, 01:54:41 pm

I'm not sure whether I can do it before the 13th (after that I won't have access to a computer until august), since it seems I will need to wrap every inline string with _ _T.. Alphabetically, I'm now at sdk/d..

(And I was wrong: I am using the Unicode version of wxWidgets, but switching to non-Unicode won't help, it will complain about typecasts anyway..)
/Per Eckerdal

Title: Mac?
Post by: mandrav on July 11, 2005, 01:57:13 pm

Quote from: per_eckerdal

I'm not sure whether I can do it before the 13th (after that I won't have access to a computer), since it seems I will need to wrap every inline string with _ _T.. Alphabetically, I'm now at sdk/d..

(And I was wrong: I am using the Unicode version of wxWidgets, but switching to non-Unicode won't help, it will complain about typecasts anyway..)
/Per Eckerdal

No problem Per.
You might benefit, if the _() patch is submitted by someone else before you can work on it again ;)

Yiannis.

Title: Mac?
Post by: per_eckerdal on July 11, 2005, 01:59:27 pm

okay. I can post what I've done later today if you're interested (and no one else has already done it?)
/Per Eckerdal