This seems to be working for me now. It involved a little poking around so I
have documented it on my bliki
(http://davelevy.dyndns.info/snipsnap/space/Dave/WINE) and here.
I started at wiki :: macosx :: Building (http://wiki.winehq.org/MacOSX/Building)
so thanks for that. Since it was recommended to make a build from source and
since I had to install a package manager of some description to get the source
code I downloaded git as recommended.
My process
* Download xcode, for 10.5, you need version 3.1.3
* Download git (I think so, now not sure if its part of MacOSX 10.5)
* Download the source using git, see wiki :: gitwine
(http://wiki.winehq.org/GitWine)
* 'make' the binary, use --disable-win16
* link the xfree libraries to /usr/lib
The last line might not be the best way to solve the problem but I tested the
install using ConTEXT and had xfree errors, but not now. Having had another look
at the wiki page, theres some advice on using
DYLD_FALLBACK_LIBRARY_PATH
which I didn't understand as pertinant because I am not a developer, which
might make the next stage fun. Is this relevant to the xfree errors problem?
I'd suggest that the wiki page documents the --disable-win16 flag on make
and if the link trick is deemed acceptable, that this is placed on the wiki page
as well. Both these tips have been documented in previous threads, which is
where I found them. Thanks
Otherwise not as painful as I'd thought.
DaveLevy wrote:> > I'd suggest that the wiki page documents the --disable-win16 flag on make and if the link trick is deemed acceptable, that this is placed on the wiki page as well. Both these tips have been documented in previous threads, which is where I found them.So change it. The wiki can be edited by anyone.
James McKenzie wrote:> DaveLevy wrote: > > > > > NB This trick was documented by someone else on this forum. > > > > > Which trick? The DYLD_FALLBACK_LIBRARY_PATH or adding the symlinks? > > The first has been documented in several places, the second I have not > seen before. > > James McKenzieI found out about the symlink hack on this thread (http://forums.macnn.com/104/alternative-operating-systems/304996/wine-wants-freetype-font-library/) at http://forums.macnn.com. My second post above tried to correct the statement you quoted; I couldn't find an edit button, I was just trying to ensure I credited my sources.
dimesio wrote:> > >DaveLevy wrote: >> >> >> I am prepared to make changes to the wiki page as suggested by dimesio above, but would again like some advice on ettiquette. This would be my first contribution to the WINE project in any way and am more used to led wikis such as media wiki or confluence where 'out of the blue' contributions are placed on a talk page or submitted as signed comments before being voted (in some way) to the front page. > > >There is no such system here. >All Wiki entries are subject to additions/deletions and overwriting at any time. All entries are subject to peer review as well. However, if you find incorrect information, please update it as well. The Wiki is way out of date in some areas and needs to be updated to current status with improved information. You do NOT need to go before a 'board' to get approval here to update the Wiki. Please be aware if you attempt to spam the Wiki, that there are backups of the Wiki pages so we can restore them (at least from what I understand as several pages had to be rolled back.) James McKenzie
DaveLevy wrote:> >James McKenzie wrote: >> DaveLevy wrote: >> >> > >> > NB This trick was documented by someone else on this forum. >> > >> > >> Which trick? The DYLD_FALLBACK_LIBRARY_PATH or adding the symlinks? >> >> The first has been documented in several places, the second I have not >> seen before. >> >> James McKenzie > > >I found out about the symlink hack on this thread (http://forums.macnn.com/104/alternative-operating-systems/304996/wine-wants- >freetype-font-library/) at http://forums.macnn.com. My second post above tried to correct the statement you quoted; I couldn't find > an edit button, I was just trying to ensure I credited my sources. >Thank you for providing the source of your information. I will attempt to get to the MacNN forums to review other ideas as well. James McKenzie>