From: Frans S. <fra...@gm...> - 2010-03-12 09:14:21
|
Hi Gustav, Thank you very much for your great contribution to usbpicprog - osx! Especially the scripts make it very easy for other mac developers to build the application. I have put them in the subversion repository under upp_wx/osx. (maybe we still need to change some cd commands in the scripts in order to run them from there). I have put the .dmg file on usbpicprog.org/downloads. Please everybody with a mac (intel or ppc), test it and report back to the mailing list! You are not breaking any rules, except that I have to accept the big attachments manually :P Maybe next time it is better if you put them on usbpicprog/downloads directly. I will send you the password, but better not through this mailin list... If you send me your sourceforge username, I can also add you to the project so that you have write access to the subversion repository in case anything needs to change for the osx build. (and of course for the official releases). Great work! Frans On Thu, 2010-03-11 at 20:34 +0100, Gustav Johansson wrote: > Hi! > > Since I'm new to this mailing-list, I apologize in advance if I break > some rules... If I do, just tell me and I won't do it again! :) > > I've been working on creating a universal build for OS X of the > usbpicprog.app, and I think I've got it now. Attached are two files, > one disk image containing a freshly built usbpicprog.app that *should* > work on both Intel and PPC Macs, from 10.4 and up. I've tested it on > an Intel 10.6 and an PPC 10.5, and they both work just fine. I do not > however have a usb-programmer yet, so I have not tested the > programming functionality. If you can help out by testing, please do > so and tell me about any problems. > > If there is an interest in it, I can setup a cron-job and built > "nigthly" builds of usbpicprog for OS X and upload the disk images to > wherever is suitable. > > The second file is a couple of scripts and a README file with > information on how you can build this yourself. I used a lot of the > info by Lukas Zeller, and only had to do a bit of tweaking to get it > to work. > > The main problem that Lukas Zeller saw was the libiconv linking, which > was almost correct. The problem is not with the MacPorts libiconv, but > rather that Apple ships with a number of libiconv versions, some of > which takes precedence over the MacPorts version. The solution is to > force wxWidgets to use the MacPorts version by using a configure flag. > For more information, see the install_wxWidgets.sh script. > > There is however another issue that can mess stuff up. libtool! Again, > Apple ships there own "special" version of libtool/libtoolize, which > is NOT compatible with the GNU version. Unfortunately, stuff breaks in > OS X if you overwrite Apple's version, and thus MacPorts have solved > this by renaming libtool to glibtool and glibtoolize. To get > everything to compile correctly, I had to make a symlink from > /opt/local/bin/glibtool to /opt/local/bin/libtool (and glibtoolize of > course). This makes everything build fine, but is a bit of a hack > since I have to remove this symlinks after the build is complete or OS > X will mess stuff up when installing other programs. The best way > would be to make the configure/autogen.sh scripts to realize that > they're building on a Mac and change from libtool to glibtool... > > I think that was all. Hope it works for everyone else as well! > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ Usbpicprog-technical mailing list Usb...@li... https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical |