Author Topic: Mac?  (Read 18217 times)

per_eckerdal

  • Guest
Mac?
« 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

Offline David Perfors

  • Developer
  • Lives here!
  • *****
  • Posts: 560
Mac?
« Reply #1 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 :)
OS: winXP
Compiler: mingw
IDE: Code::Blocks SVN WX: 2.8.4 Wish list: faster code completion, easier debugging, refactoring

per_eckerdal

  • Guest
Mac?
« Reply #2 on: July 10, 2005, 11:34:47 pm »
hehe :)

per_eckerdal

  • Guest
Mac?
« Reply #3 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

Offline David Perfors

  • Developer
  • Lives here!
  • *****
  • Posts: 560
Mac?
« Reply #4 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...
OS: winXP
Compiler: mingw
IDE: Code::Blocks SVN WX: 2.8.4 Wish list: faster code completion, easier debugging, refactoring

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Mac?
« Reply #5 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.
Be patient!
This bug will be fixed soon...

per_eckerdal

  • Guest
Mac?
« Reply #6 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

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Mac?
« Reply #7 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.
Be patient!
This bug will be fixed soon...

Offline Profic

  • Multiple posting newcomer
  • *
  • Posts: 56
Mac?
« Reply #8 on: July 11, 2005, 09:32:12 am »
AFAIR Scintilla itself didn't have port to mac...
Not fear, nor tears can reach me now, the light seems so clear as the night fades away (c) Tristania - Beyond The Veil

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Mac?
« Reply #9 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.
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...
Be patient!
This bug will be fixed soon...

per_eckerdal

  • Guest
Mac?
« Reply #10 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

per_eckerdal

  • Guest
Mac?
« Reply #11 on: July 11, 2005, 10:32:12 am »
.. and it is severely lacking a good ide :)..

per_eckerdal

  • Guest
Mac?
« Reply #12 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

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Mac?
« Reply #13 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.
Be patient!
This bug will be fixed soon...

per_eckerdal

  • Guest
Mac?
« Reply #14 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