Menu
▾
▴
usbpicprog-technical
|
From: Gustav J. <gu...@ne...> - 2010-03-11 19:34:44
|
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! -- Dr. Gustav Johansson Skrantahöjdsvägen 52A, 1tr SE-691 46 Karlskoga, Sweden +46 70 654 8666 |
|
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 |
|
From: Frans S. <fra...@gm...> - 2010-03-19 15:39:48
|
Hi Gustav, I have tried the .dmg on an intel 10.5 system, and it didn't seem to work because it was compiled using gcc 4.2. I compiled it using gcc 4.0 and modified buildmac.sh. I think the latest one does now run on 10.4, 10.5 and 10.6. Also libiconv has been included in the .app now. Cheers, 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 |
|
From: Gustav J. <gu...@ne...> - 2010-03-19 16:18:44
|
Hi Frans! I have not uploaded any of the "fixed" builds, I was going to yesterday but the FTP didn't work... I'll upload one of my snapshots tonight and we'll see if they work then. I've also managed to build for cocoa, so if you can test that build as well it would be great! Cheers, Dr. Gustav Johansson On 19 mar 2010, at 16.39, Frans Schreuder <fra...@gm...> wrote: > Hi Gustav, > > I have tried the .dmg on an intel 10.5 system, and it didn't seem to > work because it was compiled using gcc 4.2. > I compiled it using gcc 4.0 and modified buildmac.sh. > I think the latest one does now run on 10.4, 10.5 and 10.6. > Also libiconv has been included in the .app now. > > Cheers, > > 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 > > --- > --- > --- > --------------------------------------------------------------------- > 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 |
|
From: Frans S. <fra...@gm...> - 2010-03-19 16:23:50
|
Hi Gustav, As you can see in the buildmac.sh script (and also in the install_wxWidgets.sh script) I have added export MACOSX_DEPLOYMENT_TARGET=10.4 export CC="gcc-4.0" I also added libiconv.dylib because it wouldn't run if you didn't have it installed from macports. I think you will also need to build wxWidgets again with gcc-4.0 (as well as some other libraries) Could you try 869M, the one that I have uploaded to usbpicprog.org/downloads? Cheers, Frans Gustav Johansson schreef: > Hi Frans! > > I have not uploaded any of the "fixed" builds, I was going to > yesterday but the FTP didn't work... I'll upload one of my snapshots > tonight and we'll see if they work then. I've also managed to build > for cocoa, so if you can test that build as well it would be great! > > Cheers, > Dr. Gustav Johansson > > > On 19 mar 2010, at 16.39, Frans Schreuder <fra...@gm... > <mailto:fra...@gm...>> wrote: > >> Hi Gustav, >> >> I have tried the .dmg on an intel 10.5 system, and it didn't seem to >> work because it was compiled using gcc 4.2. >> I compiled it using gcc 4.0 and modified buildmac.sh. >> I think the latest one does now run on 10.4, 10.5 and 10.6. >> Also libiconv has been included in the .app now. >> >> Cheers, >> >> 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... <mailto:Usb...@li...> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >>> >> >> ------------------------------------------------------------------------------ >> 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... >> <mailto:Usb...@li...> >> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > 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 > |
|
From: Gustav J. <gu...@ne...> - 2010-03-19 16:59:08
|
Hi Frans, I'll try it tonight, I'm not at home at the moment... Cheers, Dr. Gustav Johansson On 19 mar 2010, at 17.23, Frans Schreuder <fra...@gm...> wrote: > Hi Gustav, > > As you can see in the buildmac.sh script (and also in the > install_wxWidgets.sh script) I have added > > export MACOSX_DEPLOYMENT_TARGET=10.4 > export CC="gcc-4.0" > > I also added libiconv.dylib because it wouldn't run if you didn't have > it installed from macports. > I think you will also need to build wxWidgets again with gcc-4.0 (as > well as some other libraries) > > Could you try 869M, the one that I have uploaded to > usbpicprog.org/downloads? > > Cheers, > > Frans > > > Gustav Johansson schreef: >> Hi Frans! >> >> I have not uploaded any of the "fixed" builds, I was going to >> yesterday but the FTP didn't work... I'll upload one of my snapshots >> tonight and we'll see if they work then. I've also managed to build >> for cocoa, so if you can test that build as well it would be great! >> >> Cheers, >> Dr. Gustav Johansson >> >> >> On 19 mar 2010, at 16.39, Frans Schreuder <fra...@gm... >> <mailto:fra...@gm...>> wrote: >> >>> Hi Gustav, >>> >>> I have tried the .dmg on an intel 10.5 system, and it didn't seem to >>> work because it was compiled using gcc 4.2. >>> I compiled it using gcc 4.0 and modified buildmac.sh. >>> I think the latest one does now run on 10.4, 10.5 and 10.6. >>> Also libiconv has been included in the .app now. >>> >>> Cheers, >>> >>> 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... >>>> <mailto:Usb...@li...> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >>>> >>> >>> --- >>> --- >>> --- >>> --- >>> ------------------------------------------------------------------ >>> 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... >>> <mailto:Usb...@li...> >>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >> --- >> --------------------------------------------------------------------- >> >> --- >> --- >> --- >> --------------------------------------------------------------------- >> 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 >> > > > --- > --- > --- > --------------------------------------------------------------------- > 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 |
|
From: Frans S. <fra...@gm...> - 2010-03-23 15:31:42
|
Hi Gustav, I have tried your build on a clean osx 10.5 system. Both the cocoa and the normal build give the same error about libiconv. I am affraid that the libiconv.dylib that you have installed was either not built universal, or it was built using gcc 4.2. I have also built the latest revision r876 wich does seem to run on a clean system. This version seems to work fine (I also fixed the configuration flags appearance) UsbPicProg-OSX-rexported.dmg (UsbPicProg-OSX-Cocoa-r872.dmg - buld gives the same error report) Process: usbpicprog [770] Path: /Volumes/UsbPicProg/usbpicprog.app/Contents/MacOS/usbpicprog Identifier: org.usbpicprog Version: ??? (???) Code Type: X86 (Native) Parent Process: launchd [92] Date/Time: 2010-03-23 08:11:43.203 -0700 OS Version: Mac OS X 10.5.2 (9C31) Report Version: 6 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Crashed Thread: 0 Dyld Error Message: Library not loaded: @executable_path/../SharedSupport/libiconv.dylib Referenced from: /Volumes/UsbPicProg/usbpicprog.app/Contents/MacOS/usbpicprog Reason: Incompatible library version: usbpicprog requires version 8.0.0 or later, but libiconv.2.dylib provides version 7.0.0 Regards, Frans On Fri, 2010-03-19 at 23:56 +0100, Gustav Johansson wrote: > Hi Frans, > > tried your build now, and it seems to work fine! Although I think that > what you've added was added already. In the end of each ./configure > line I had put in the CC=gcc+4.0 and the DEPLOYMENT_TARGET is set via > the $sdk_flags. But better safe than sorry, right? ;) > > I've just uploaded two snapshot version of the r872, one carbon (named > rexported due to a typo, already fixed and commited, but I want to > test my nightly scripts, so hopfully there will be two r873 builds in > the morning) and one cocoa. Please test them and see if they work. > They do work on my Intel 10.6 and on my PPC 10.5. But they both have > MacPorts installed, so I can't (or haven't, at least) tested them for > library content... > > Cheers, > Gustav > > On Fri, Mar 19, 2010 at 5:33 PM, Gustav Johansson <gu...@ne...> wrote: > > Hi Frans, > > > > I'll try it tonight, I'm not at home at the moment... > > > > Cheers, > > Dr. Gustav Johansson > > > > > > On 19 mar 2010, at 17.23, Frans Schreuder <fra...@gm...> wrote: > > > >> Hi Gustav, > >> > >> As you can see in the buildmac.sh script (and also in the > >> install_wxWidgets.sh script) I have added > >> > >> export MACOSX_DEPLOYMENT_TARGET=10.4 > >> export CC="gcc-4.0" > >> > >> I also added libiconv.dylib because it wouldn't run if you didn't have > >> it installed from macports. > >> I think you will also need to build wxWidgets again with gcc-4.0 (as > >> well as some other libraries) > >> > >> Could you try 869M, the one that I have uploaded to > >> usbpicprog.org/downloads? > >> > >> Cheers, > >> > >> Frans > >> > >> > >> Gustav Johansson schreef: > >>> > >>> Hi Frans! > >>> > >>> I have not uploaded any of the "fixed" builds, I was going to > >>> yesterday but the FTP didn't work... I'll upload one of my snapshots > >>> tonight and we'll see if they work then. I've also managed to build > >>> for cocoa, so if you can test that build as well it would be great! > >>> > >>> Cheers, > >>> Dr. Gustav Johansson > >>> > >>> > >>> On 19 mar 2010, at 16.39, Frans Schreuder <fra...@gm... > >>> <mailto:fra...@gm...>> wrote: > >>> > >>>> Hi Gustav, > >>>> > >>>> I have tried the .dmg on an intel 10.5 system, and it didn't seem to > >>>> work because it was compiled using gcc 4.2. > >>>> I compiled it using gcc 4.0 and modified buildmac.sh. > >>>> I think the latest one does now run on 10.4, 10.5 and 10.6. > >>>> Also libiconv has been included in the .app now. > >>>> > >>>> Cheers, > >>>> > >>>> 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... > >>>>> <mailto:Usb...@li...> > >>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > >>>>> > >>>> > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> 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... > >>>> <mailto:Usb...@li...> > >>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > >>> > >>> ------------------------------------------------------------------------ > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> 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 > >>> > >> > >> > >> > >> ------------------------------------------------------------------------------ > >> 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 > > > > > |
|
From: Gustav J. <gu...@ne...> - 2010-03-23 18:27:15
|
Hi Frans, I apologize for not telling you that those two were broken. I noticed when I checked the files after I uploaded them and the libiconv.dylib is actually missing in them, and I believe the error is due to that rather than being the wrong version. The problem was the line in the script which loops through the libraries to install, it did not end with a space and thus did only install the first library. It has been fixed and both libraries are installed properly now. Since I did this, I have set up a "nightly" script that builds if the svn has been updated, but it has taken me a couple of days since I managed a careless rm * instead of rm *~... so I had to start over. Both builds *should* be uploaded tonight at about 3:45 AM CET. Hopefully, they will both work. In addition, I noticed that the cocoa-version for x86_64 did not build properly when set for 10.4 compatibility. I assume it is because 10.4 did not actually have support for 64-bit Intel. This has also been fixed now by using different compatibility settings for ppc/i386 vs. x86_64. I'll check the nightly build tomorrow morning, and if they seem to be working, I'll send you a mail and it would be great if you could check those again then to see if I managed to get everything right in the nightly scripts. Regards, Gustav On Tue, Mar 23, 2010 at 4:31 PM, Frans Schreuder <fra...@gm...> wrote: > Hi Gustav, > > I have tried your build on a clean osx 10.5 system. Both the cocoa and the > normal build give the same error about libiconv. I am affraid that the > libiconv.dylib that you have installed was either not built universal, or it > was built using gcc 4.2. > I have also built the latest revision r876 wich does seem to run on a clean > system. This version seems to work fine (I also fixed the configuration > flags appearance) > > > UsbPicProg-OSX-rexported.dmg (UsbPicProg-OSX-Cocoa-r872.dmg - buld gives > the same error report) > > Process: usbpicprog [770] > Path: > /Volumes/UsbPicProg/usbpicprog.app/Contents/MacOS/usbpicprog > Identifier: org.usbpicprog > Version: ??? (???) > Code Type: X86 (Native) > Parent Process: launchd [92] > > Date/Time: 2010-03-23 08:11:43.203 -0700 > OS Version: Mac OS X 10.5.2 (9C31) > Report Version: 6 > > Exception Type: EXC_BREAKPOINT (SIGTRAP) > Exception Codes: 0x0000000000000002, 0x0000000000000000 > Crashed Thread: 0 > > Dyld Error Message: > Library not loaded: @executable_path/../SharedSupport/libiconv.dylib > Referenced from: > /Volumes/UsbPicProg/usbpicprog.app/Contents/MacOS/usbpicprog > Reason: Incompatible library version: usbpicprog requires version 8.0.0 or > later, but libiconv.2.dylib provides version 7.0.0 > > > Regards, > > Frans > > On Fri, 2010-03-19 at 23:56 +0100, Gustav Johansson wrote: > > Hi Frans, > > tried your build now, and it seems to work fine! Although I think that > what you've added was added already. In the end of each ./configure > line I had put in the CC=gcc+4.0 and the DEPLOYMENT_TARGET is set via > the $sdk_flags. But better safe than sorry, right? ;) > > I've just uploaded two snapshot version of the r872, one carbon (named > rexported due to a typo, already fixed and commited, but I want to > test my nightly scripts, so hopfully there will be two r873 builds in > the morning) and one cocoa. Please test them and see if they work. > They do work on my Intel 10.6 and on my PPC 10.5. But they both have > MacPorts installed, so I can't (or haven't, at least) tested them for > library content... > > Cheers, > Gustav > > On Fri, Mar 19, 2010 at 5:33 PM, Gustav Johansson <gu...@ne...> wrote: >> Hi Frans, >> >> I'll try it tonight, I'm not at home at the moment... >> >> Cheers, >> Dr. Gustav Johansson >> >> >> On 19 mar 2010, at 17.23, Frans Schreuder <fra...@gm...> >> wrote: >> >>> Hi Gustav, >>> >>> As you can see in the buildmac.sh script (and also in the >>> install_wxWidgets.sh script) I have added >>> >>> export MACOSX_DEPLOYMENT_TARGET=10.4 >>> export CC="gcc-4.0" >>> >>> I also added libiconv.dylib because it wouldn't run if you didn't have >>> it installed from macports. >>> I think you will also need to build wxWidgets again with gcc-4.0 (as >>> well as some other libraries) >>> >>> Could you try 869M, the one that I have uploaded to >>> usbpicprog.org/downloads? >>> >>> Cheers, >>> >>> Frans >>> >>> >>> Gustav Johansson schreef: >>>> >>>> Hi Frans! >>>> >>>> I have not uploaded any of the "fixed" builds, I was going to >>>> yesterday but the FTP didn't work... I'll upload one of my snapshots >>>> tonight and we'll see if they work then. I've also managed to build >>>> for cocoa, so if you can test that build as well it would be great! >>>> >>>> Cheers, >>>> Dr. Gustav Johansson >>>> >>>> >>>> On 19 mar 2010, at 16.39, Frans Schreuder <fra...@gm... >>>> <mailto:fra...@gm...>> wrote: >>>> >>>>> Hi Gustav, >>>>> >>>>> I have tried the .dmg on an intel 10.5 system, and it didn't seem to >>>>> work because it was compiled using gcc 4.2. >>>>> I compiled it using gcc 4.0 and modified buildmac.sh. >>>>> I think the latest one does now run on 10.4, 10.5 and 10.6. >>>>> Also libiconv has been included in the .app now. >>>>> >>>>> Cheers, >>>>> >>>>> 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... >>>>>> <mailto:Usb...@li...> >>>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >>>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> 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... >>>>> <mailto:Usb...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 >> > > > > > > ------------------------------------------------------------------------------ > 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 > > -- Dr. Gustav Johansson Skrantahöjdsvägen 52A, 1tr SE-691 46 Karlskoga, Sweden +46 70 654 8666 |
|
From: Frans S. <fra...@gm...> - 2010-03-24 14:42:04
Attachments:
osx-report-876.txt
|
Hi Gustav, It still doesn't work, still with the same error messages (see attachment). If I copy the .dylib files from http://usbpicprog.org/downloads/UsbPicProg-OSX-r876M.dmg (built by me) to UsbPicProg-OSX-r876.dmg, the application runs fine, so it has been built using the right compiler settings! However your libusb and libiconv dylibs are either 64 bit or built using gcc 4.2. Copying the files to the cocoa app doesn't help. I guess, I do need 64 bit libraries for that (?) btw, I have one more question: Do we really need the cocoa version? How does it work, or is it still quite buggy? The normal version appears very fine to me! Cheers, Frans On 3/23/2010 19:27, Gustav Johansson wrote: > Hi Frans, > > I apologize for not telling you that those two were broken. I noticed > when I checked the files after I uploaded them and the libiconv.dylib > is actually missing in them, and I believe the error is due to that > rather than being the wrong version. The problem was the line in the > script which loops through the libraries to install, it did not end > with a space and thus did only install the first library. It has been > fixed and both libraries are installed properly now. > > Since I did this, I have set up a "nightly" script that builds if the > svn has been updated, but it has taken me a couple of days since I > managed a careless rm * instead of rm *~... so I had to start over. > Both builds *should* be uploaded tonight at about 3:45 AM CET. > Hopefully, they will both work. > > In addition, I noticed that the cocoa-version for x86_64 did not build > properly when set for 10.4 compatibility. I assume it is because 10.4 > did not actually have support for 64-bit Intel. This has also been > fixed now by using different compatibility settings for ppc/i386 vs. > x86_64. > > I'll check the nightly build tomorrow morning, and if they seem to be > working, I'll send you a mail and it would be great if you could check > those again then to see if I managed to get everything right in the > nightly scripts. > > Regards, > Gustav > > > On Tue, Mar 23, 2010 at 4:31 PM, Frans Schreuder > <fra...@gm...> wrote: > >> Hi Gustav, >> >> I have tried your build on a clean osx 10.5 system. Both the cocoa and the >> normal build give the same error about libiconv. I am affraid that the >> libiconv.dylib that you have installed was either not built universal, or it >> was built using gcc 4.2. >> I have also built the latest revision r876 wich does seem to run on a clean >> system. This version seems to work fine (I also fixed the configuration >> flags appearance) >> >> >> UsbPicProg-OSX-rexported.dmg (UsbPicProg-OSX-Cocoa-r872.dmg - buld gives >> the same error report) >> >> Process: usbpicprog [770] >> Path: >> /Volumes/UsbPicProg/usbpicprog.app/Contents/MacOS/usbpicprog >> Identifier: org.usbpicprog >> Version: ??? (???) >> Code Type: X86 (Native) >> Parent Process: launchd [92] >> >> Date/Time: 2010-03-23 08:11:43.203 -0700 >> OS Version: Mac OS X 10.5.2 (9C31) >> Report Version: 6 >> >> Exception Type: EXC_BREAKPOINT (SIGTRAP) >> Exception Codes: 0x0000000000000002, 0x0000000000000000 >> Crashed Thread: 0 >> >> Dyld Error Message: >> Library not loaded: @executable_path/../SharedSupport/libiconv.dylib >> Referenced from: >> /Volumes/UsbPicProg/usbpicprog.app/Contents/MacOS/usbpicprog >> Reason: Incompatible library version: usbpicprog requires version 8.0.0 or >> later, but libiconv.2.dylib provides version 7.0.0 >> >> >> Regards, >> >> Frans >> >> On Fri, 2010-03-19 at 23:56 +0100, Gustav Johansson wrote: >> >> Hi Frans, >> >> tried your build now, and it seems to work fine! Although I think that >> what you've added was added already. In the end of each ./configure >> line I had put in the CC=gcc+4.0 and the DEPLOYMENT_TARGET is set via >> the $sdk_flags. But better safe than sorry, right? ;) >> >> I've just uploaded two snapshot version of the r872, one carbon (named >> rexported due to a typo, already fixed and commited, but I want to >> test my nightly scripts, so hopfully there will be two r873 builds in >> the morning) and one cocoa. Please test them and see if they work. >> They do work on my Intel 10.6 and on my PPC 10.5. But they both have >> MacPorts installed, so I can't (or haven't, at least) tested them for >> library content... >> >> Cheers, >> Gustav >> >> On Fri, Mar 19, 2010 at 5:33 PM, Gustav Johansson<gu...@ne...> wrote: >> >>> Hi Frans, >>> >>> I'll try it tonight, I'm not at home at the moment... >>> >>> Cheers, >>> Dr. Gustav Johansson >>> >>> >>> On 19 mar 2010, at 17.23, Frans Schreuder<fra...@gm...> >>> wrote: >>> >>> >>>> Hi Gustav, >>>> >>>> As you can see in the buildmac.sh script (and also in the >>>> install_wxWidgets.sh script) I have added >>>> >>>> export MACOSX_DEPLOYMENT_TARGET=10.4 >>>> export CC="gcc-4.0" >>>> >>>> I also added libiconv.dylib because it wouldn't run if you didn't have >>>> it installed from macports. >>>> I think you will also need to build wxWidgets again with gcc-4.0 (as >>>> well as some other libraries) >>>> >>>> Could you try 869M, the one that I have uploaded to >>>> usbpicprog.org/downloads? >>>> >>>> Cheers, >>>> >>>> Frans >>>> >>>> >>>> Gustav Johansson schreef: >>>> >>>>> Hi Frans! >>>>> >>>>> I have not uploaded any of the "fixed" builds, I was going to >>>>> yesterday but the FTP didn't work... I'll upload one of my snapshots >>>>> tonight and we'll see if they work then. I've also managed to build >>>>> for cocoa, so if you can test that build as well it would be great! >>>>> >>>>> Cheers, >>>>> Dr. Gustav Johansson >>>>> >>>>> >>>>> On 19 mar 2010, at 16.39, Frans Schreuder<fra...@gm... >>>>> <mailto:fra...@gm...>> wrote: >>>>> >>>>> >>>>>> Hi Gustav, >>>>>> >>>>>> I have tried the .dmg on an intel 10.5 system, and it didn't seem to >>>>>> work because it was compiled using gcc 4.2. >>>>>> I compiled it using gcc 4.0 and modified buildmac.sh. >>>>>> I think the latest one does now run on 10.4, 10.5 and 10.6. >>>>>> Also libiconv has been included in the .app now. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> 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... >>>>>>> <mailto:Usb...@li...> >>>>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> 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... >>>>>> <mailto:Usb...@li...> >>>>>> https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical >>>>>> >>>>> ------------------------------------------------------------------------ >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> 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 >>>>> >>>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> 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 >>>> >>> >> >> >> >> >> ------------------------------------------------------------------------------ >> 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 >> >> >> > > > |
|
From: Frans S. <fra...@gm...> - 2010-03-23 15:33:42
|
Dear all, I think the latest version of usbpicprog 876 seems to be running quite stable on all systems (win 32 / 64, osx universal and ubuntu) What do you think, is it time for a beta release of version 0.3.1? Frans |
|
From: Francesco <f18...@ya...> - 2010-03-25 22:36:24
|
Hi, 2010/3/23 Frans Schreuder <fra...@gm...>: > I think the latest version of usbpicprog 876 seems to be running quite > stable on all systems (win 32 / 64, osx universal and ubuntu) > What do you think, is it time for a beta release of version 0.3.1? Unfortunately I had no much time to fiddle with real PICs on breadboards recently... I'll try to test my latest PICs (18f2550, 18f4553) in the weekend. Anyway I think it's fine to make at least a beta of 0.3.1. However I wonder if it wouldn't be better to call the new release 0.4.0 since the major upgrade from libusb-0.1 to libusb-1.0... Francesco |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X