From: Dave R. <dav...@ma...> - 2002-05-15 00:00:53
|
I'm trying my hand at this using the latest CVS versions of wxMAC and wxPerl. a couple of months ago... my previous attempt at installing wxMAC was unsuccessful. everything appeared to compile and install, and running the minimal sample brought up a window, yet I was unable to interact with it. my previous attempt at installing wxPerl (0.10, along with the previous attempt at wxMAC) appeared to compile and install. I've never been able to run the wxPerl minimal sample, although perl -c minimal.pl would compile. and now... my latest attempt at installing wxMAC appears to have been successful. the above problems are no longer apparent and all the samples I have run appear to work as expected. my latest attempts at installing wxPerl (0.10 and 0.11) are not going well, but giving different results. I gave up trying to install 0.10 as it appears MenuItems work differently. as my previous attempt compiled (yet didn't run), I assumed that wxMAC had changed and that I would need wxPerl 0.11 to continue. when trying to get 0.11 to compile, I found the following: 1) /distrib/mac/shared-ld-sh the Makefiles that Makefile.PL outputs contains this reference. under 0.10, the output used to be "c++ -shared". 2) wxRegion::Offset Wx.c: In function `void XS_Wx__Region_Offset(CV *)': Wx.c:7100: no matching function for call to `wxRegion::Offset (wxCoord &, wxCoord &)' 3) ColourDialog Frames.c: In function `void XS_Wx__ColourDialog_new(CV *)': Frames.c:5330: invalid use of undefined type `class Wx_ColourDialog' cpp/typedef.h:140: forward declaration of `class Wx_ColourDialog' Frames.c:5332: type `wxObject' is not a base type for type `Wx_ColourDialog' XS/ColourDialog.xs: In function `void XS_Wx__ColourDialog_GetColourData(CV *)': XS/ColourDialog.xs:25: invalid use of undefined type `class wxGenericColourDialog' cpp/typedef.h:140: forward declaration of `class wxGenericColourDialog' Frames.c: In function `void XS_Wx__ColourDialog_ShowModal(CV *)': Frames.c:5370: invalid use of undefined type `class wxGenericColourDialog' cpp/typedef.h:140: forward declaration of `class wxGenericColourDialog' 4) Wx_Cursor *newImage() XS/Cursor.xs: In function `void XS_Wx__Cursor_newImage(CV *)': XS/Cursor.xs:46: no matching function for call to `wxCursor::wxCursor (wxImage &)' 5) Wx_Icon::LoadFile() XS/Icon.xs: In function `void XS_Wx__Icon_LoadFile(CV *)': XS/Icon.xs:99: no matching function for call to `wxIcon::LoadFile (wxString &, long int &)' 6) Wx_Bitmap::SetMask() XS/Bitmap.xs: In function `void XS_Wx__Bitmap_SetMask(CV *)': /usr/local/include/wx/mac/bitmap.h:35: `wxMask::wxMask(const wxMask &)' is private XS/Bitmap.xs:328: within this context having "worked around" those, I got everything to compile without other errors. unsurprisingly, perl minimal.pl still compiles but fails to display a window. I would very much like to see wxPerl running under OS X and am available to any extent to help with compiling, test, debugging. I hope the above is helpful - please let me know what other steps I can take to help. regards, /dave |
From: Mattia B. <mb...@ds...> - 2002-05-15 07:03:23
|
On Tue, 14 May 2002, Dave Roe wrote: >I'm trying my hand at this using the latest CVS versions of wxMAC and >wxPerl. > >6) Wx_Bitmap::SetMask() >XS/Bitmap.xs: In function `void XS_Wx__Bitmap_SetMask(CV *)': >/usr/local/include/wx/mac/bitmap.h:35: `wxMask::wxMask(const wxMask &)' >is private >XS/Bitmap.xs:328: within this context Will ( try to ) correct. >having "worked around" those, I got everything to compile without other >errors. unsurprisingly, perl minimal.pl still compiles but fails to >display a window. > >I would very much like to see wxPerl running under OS X and am available >to any extent to help with compiling, test, debugging. I hope the above >is helpful - please let me know what other steps I can take to help. I think ( not having a Mac, anc knowing almost nothing about Mac ) that you need to compile Perl as a Mac App. wxPython folks did that ( compiling the Python interpreter as a Mac App ) and it worked. Details are in the wxpython-mac archives ( http://lists.wxwindows.org/ ). The idea is: 1) follow the instructions to build Python as a Mac App ./configure --with-frameworks # or something like this cd Mac/OSX make -n |less and look at the output of the last command 2) try to do that to perl ./Configure # answer a lot of questions make # look at the step when it links the perl executable # and try to modify it to do what Python does Regards Mattia |
From: Dave R. <dav...@ma...> - 2002-05-15 10:53:02
|
ok, I've read the mailing list and have compiled Python.app as described. I saw the tail of the output, and planned to make such modifications to the Perl compilation, but right now I'm having problems getting Perl to compile at all under OS X. it's late, so I'll have another go tomorrow, but I'm concerned that this may prove problematic. the fact is, OS X comes with Perl 5.6.0, so few people perhaps will have bothered to re-compile Perl. we'll see... /dave On Wednesday, May 15, 2002, at 12:03 , Mattia Barbon wrote: > On Tue, 14 May 2002, Dave Roe wrote: > >> I'm trying my hand at this using the latest CVS versions of wxMAC and >> wxPerl. >> >> 6) Wx_Bitmap::SetMask() >> XS/Bitmap.xs: In function `void XS_Wx__Bitmap_SetMask(CV *)': >> /usr/local/include/wx/mac/bitmap.h:35: `wxMask::wxMask(const wxMask &)' >> is private >> XS/Bitmap.xs:328: within this context > Will ( try to ) correct. > >> having "worked around" those, I got everything to compile without other >> errors. unsurprisingly, perl minimal.pl still compiles but fails to >> display a window. >> >> I would very much like to see wxPerl running under OS X and am >> available >> to any extent to help with compiling, test, debugging. I hope the above >> is helpful - please let me know what other steps I can take to help. > I think ( not having a Mac, anc knowing almost nothing about Mac ) > that you need to compile Perl as a Mac App. wxPython folks did that > ( compiling the Python interpreter as a Mac App ) and it worked. > Details are in the wxpython-mac archives > ( http://lists.wxwindows.org/ ). > > The idea is: > 1) follow the instructions to build Python as a Mac App > ./configure --with-frameworks # or something like this > cd Mac/OSX > make -n |less > > and look at the output of the last command > 2) try to do that to perl > ./Configure # answer a lot of questions > make > # look at the step when it links the perl executable > # and try to modify it to do what Python does > > Regards > Mattia > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We > supply > the hardware. You get the recognition. Email Us: > ban...@so... > _______________________________________________ > wxperl-users mailing list > wxp...@li... > https://lists.sourceforge.net/lists/listinfo/wxperl-users > > -------------------------------- 8< -------------------------------- pls note - new contact details: email: dav...@ma... phone: (650) 906 3497 dav...@em... is still a valid email address |
From: Mattia B. <mb...@ds...> - 2002-05-15 19:47:06
|
> ok, I've read the mailing list and have compiled Python.app as > described. I saw the tail of the output, and planned to make such > modifications to the Perl compilation, but right now I'm having problems > getting Perl to compile at all under OS X. it's late, so I'll have > another go tomorrow, but I'm concerned that this may prove problematic. > the fact is, OS X comes with Perl 5.6.0, so few people perhaps will have > bothered to re-compile Perl. we'll see... You may try the developement branch, available via rsync ( perldoc perlhack for more information ), or there are snapshots http://www.iki.fi/jhi/pe...@16...z http://www.iki.fi/jhi/perl@16611.tbz ftp://ftp.funet.fi/pub/languages/perl/snap/pe...@16...z ftp://ftp.funet.fi/pub/languages/perl/snap/perl@16611.tbz It should work OOTB on OS X, and AFAICS it is reasonably stable Regards Mattia |
From: Dave R. <dav...@ma...> - 2002-05-15 20:00:16
|
my problem is most likely one of case-sensitivity. after running "Configure", I have no Makefile. this is because OS X does _not_ distinguish between "Makefile" and "makefile" yet the shell scripts use both names as part of the process. I have to find a way of changing one of them. /dave On Wednesday, May 15, 2002, at 12:45 , Mattia Barbon wrote: >> ok, I've read the mailing list and have compiled Python.app as >> described. I saw the tail of the output, and planned to make such >> modifications to the Perl compilation, but right now I'm having >> problems >> getting Perl to compile at all under OS X. it's late, so I'll have >> another go tomorrow, but I'm concerned that this may prove problematic. >> the fact is, OS X comes with Perl 5.6.0, so few people perhaps will >> have >> bothered to re-compile Perl. we'll see... > You may try the developement branch, available via rsync ( perldoc > perlhack > for more information ), or there are snapshots > http://www.iki.fi/jhi/pe...@16...z > http://www.iki.fi/jhi/perl@16611.tbz > > ftp://ftp.funet.fi/pub/languages/perl/snap/pe...@16...z > ftp://ftp.funet.fi/pub/languages/perl/snap/perl@16611.tbz > > It should work OOTB on OS X, and AFAICS it is reasonably stable > > Regards > Mattia > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We > supply > the hardware. You get the recognition. Email Us: > ban...@so... > _______________________________________________ > wxperl-users mailing list > wxp...@li... > https://lists.sourceforge.net/lists/listinfo/wxperl-users > > -------------------------------- 8< -------------------------------- pls note - new contact details: email: dav...@ma... phone: (650) 906 3497 dav...@em... is still a valid email address |
From: Dave R. <dav...@ma...> - 2002-05-15 22:24:41
|
ok, using information found at http://duke.usask.ca/~dalglb/macosx/Perl_5.6.html, I was able to compile perl-5.6.1. the following appears to be the relevant part of the Python.app compile: cc -framework System -framework Python -framework Carbon -framework Foundation ../../Mac/Python/macmain.o ../../Mac/Python/macgetargv.o -o pythonforbundle I now have to find the relevant part of the perl compile to put these compiler options on, right? this looks like it could be it: env LD_RUN_PATH=/System/Library/Perl/darwin/CORE DYLD_LIBRARY_PATH=/Users/dave/Desktop/perl-5.6.1 cc -o perl -flat_namespace -L/usr/local/lib perlmain.o more later, /dave |
From: Dave R. <dav...@ma...> - 2002-05-15 23:14:24
|
I was able to compile a perlforbundle binary using the -framework compiler options, but I imagine it's just the tip of the iceberg. the resulting binary appears no different from the perl binary. I'd imagine I have to pick a whole bunch of framework libraries to link against instead of the current LDLIBRARY value. any pointers? /dave On Wednesday, May 15, 2002, at 03:24 , Dave Roe wrote: > ok, using information found at > http://duke.usask.ca/~dalglb/macosx/Perl_5.6.html, I was able to > compile perl-5.6.1. > > the following appears to be the relevant part of the Python.app compile: > > cc -framework System -framework Python -framework Carbon -framework > Foundation ../../Mac/Python/macmain.o ../../Mac/Python/macgetargv.o -o > pythonforbundle > > I now have to find the relevant part of the perl compile to put these > compiler options on, right? > > this looks like it could be it: > > env LD_RUN_PATH=/System/Library/Perl/darwin/CORE > DYLD_LIBRARY_PATH=/Users/dave/Desktop/perl-5.6.1 cc -o perl > -flat_namespace -L/usr/local/lib perlmain.o > > more later, > /dave > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We > supply > the hardware. You get the recognition. Email Us: > ban...@so... > _______________________________________________ > wxperl-users mailing list > wxp...@li... > https://lists.sourceforge.net/lists/listinfo/wxperl-users > > -------------------------------- 8< -------------------------------- pls note - new contact details: email: dav...@ma... phone: (650) 906 3497 dav...@em... is still a valid email address |
From: Mattia B. <mb...@ds...> - 2002-05-16 06:53:39
|
On Wed, 15 May 2002, Dave Roe wrote: >ok, using information found at >http://duke.usask.ca/~dalglb/macosx/Perl_5.6.html, I was able to compile >perl-5.6.1. > >the following appears to be the relevant part of the Python.app compile: > >cc -framework System -framework Python -framework Carbon -framework >Foundation ../../Mac/Python/macmain.o ../../Mac/Python/macgetargv.o -o >pythonforbundle > >I now have to find the relevant part of the perl compile to put these >compiler options on, right? > >this looks like it could be it: > >env LD_RUN_PATH=/System/Library/Perl/darwin/CORE >DYLD_LIBRARY_PATH=/Users/dave/Desktop/perl-5.6.1 cc -o perl >-flat_namespace -L/usr/local/lib perlmain.o Correct, but I think the most important part is the part done by Mac/OSX/Makefile; when it creates a directory named Python.App ( IIRC ), and copies some icons/resources/things into it. Regards Mattia |
From: Mattia B. <mb...@ds...> - 2002-05-16 06:48:23
|
On Wed, 15 May 2002, Dave Roe wrote: >my problem is most likely one of case-sensitivity. after running >"Configure", I have no Makefile. this is because OS X does _not_ >distinguish between "Makefile" and "makefile" yet the shell scripts use >both names as part of the process. I have to find a way of changing one >of them. Well, I don't know anything about OS X, but I know people are routinely compiling the snapshots under OS X, so if you can afford the download, it may be worth trying; I think whatever problems there are with case injsensitivity may be addressed in the developement branch, so you don't need to change shell scripts & co. Regards Mattia |