Re: [Usbpicprog-technical] [usbpicprog-technical] Contact: Mac OS X PPC Compile

[Frans S. <fra...@gm...>]

Dear Aleksej,

On Thu, 2010-03-04 at 17:05 +0100, Aleksej Horvat wrote:

> Dear Frans,
> 
> Attached is the compiled app, with libraries included.  I would also  
> be willing to compile future versions for the website if you like.

Thank you very much. I have put it on usbpicprog.org/downloads, so that
other people having a ppc mac  can test it as well.

> 
> Regarding the language issue, I resolved it by manually deleting the  
> NL files, however this is actually a bug, at least on OS X.  My system  
> language is correctly set to English as primary language, however my  
> region settings are for Nederland because this matches my keyboard and  
> date settings here in Holland.  While this may not be the case for  
> everyone to mix and match, it is an independent setting, and programs  
> running on Mac should respect the system language preference, and then  
> optionally regional date or number formatting where appropriate  
> (calendar, spreadsheets, etc.)  I haven't checked the code yet to see  
> how the language is determined.

This is just one line of code in usbpicprog and it is determined by
wxWidgets. If it is a bug, it must be in wxWidgets.

> 
> Also, I'm not sure if this is a known bug, or mac specific, but the  
> frame with program/memory space display, etc. does not resize with the  
> window.  Apparently it is calculated on at launch based on the last  
> known window size.  While easy to work around, still rather annoying.

Yes, I know about this and there is a workaround, but you will need the
next wxWidgets (2.9.1) for it to compile.

> 
> Lastly, I was curious about the firmware.  As stated is based on the  
> picdem bootloader, so I naively attempted to let piklab recognize it,  
> and failed.  Is that possible?

There are two pieces of firmware, the bootloader and the usbpicprog
firmware. piklab can communicate with the bootloader which is indeed the
picdem bootloader with a few modifications. (you have to put just one of
the two jumpers in order to run the bootloader in stead of the
usbpicprog-firmware)

> 
> Anyway, thanks sincerely for all you help getting this running.
> Aleksej Horvat


Thanks,

Frans Schreuder

> On 3 mrt 2010, at 16:16, Frans Schreuder wrote:
> 
> > Dear Aleksej,
> >
> > Yes, I would like to have the binary. Could you zip the .app file  
> > with the right version information?
> > eg:
> > usbpicprog-831-20100303-osx-ppc.app.zip
> >
> > The program runs in Dutch only if you have a flag set somewhere that  
> > your system should run programs in Dutch.
> > Probably something like LC_LANG = nl_NL.UTF-8 or LC_ALL=nl_NL.UTF-8
> > I don't exactly know how to do this setting in osx, but it must be  
> > defined somewhere.
> > If you can't find the setting, you can always delete the nl.mo file  
> > from the .app file to run it in English.
> >
> > Kind regards,
> >
> > Frans Schreuder
> >
> >
> > On 3/3/2010 15:18, Aleksej Horvat wrote:
> >> Dear Frans,
> >>
> >> I have finally suceded in compiling on my system.  It seems that  
> >> even after your changes, there were some problems on system  
> >> regarding the correct flags for wxwidgets.  I could send you a  
> >> compiled binary to add to the project page if you like, just let me  
> >> know.
> >>
> >> One last question, the version I compiled defaults to Dutch, even  
> >> though my system is set to English language.  I don't see a setting  
> >> to change this value.  Must I pass a flag at compile time?
> >>
> >> Thanks
> >> Aleksej
> >>
> >> On 28 feb 2010, at 12:54, Frans Schreuder wrote:
> >>
> >>> Aleksej Horvat schreef:
> >>>
> >>> Dear Aleksej,
> >>>
> >>> I have committed them to SVN and also here: http://usbpicprog.org/downloads/usbpicprog-831-20100226.tar.gz
> >>> Also buildmac.sh is changed, so you should just be able to run it  
> >>> as it is!
> >>>
> >>> Kind regards,
> >>>
> >>> Frans Schreuder
> >>>> Dear Frans,
> >>>>
> >>>> Thank you for taking the time to look into the problem.  I'm glad  
> >>>> to hear that you were able to compile successfully.   
> >>>> Unfortunately, I am not able to use the package because I am  
> >>>> running a PPC mac.  The changes you mentioned, have you committed  
> >>>> them to the svn? or do have to change them manually?
> >>>>
> >>>> Thanks again,
> >>>> Aleksej
> >>>>
> >>>> On 26 feb 2010, at 14:25, Frans Schreuder wrote:
> >>>>
> >>>>> Dear Aleksej,
> >>>>>
> >>>>> I have succeeded to build the latest snapshot (831) with osx  
> >>>>> 10.5, you can find the package here (I hope it works on your mac  
> >>>>> too):
> >>>>> http://usbpicprog.org/downloads/usbpicprog-831-20100226- 
> >>>>> osx.app.zip
> >>>>>
> >>>>> There were some things that I had to change in the usbpicprog  
> >>>>> archive:
> >>>>> -There were some cout<<wxString statements in the source code.  
> >>>>> This works in Linux and Windows, but the osx gcc compiler has  
> >>>>> some problems with it, so I had to change it to wxString.mb_str()
> >>>>> -on Windows, there was a function in libusb called  
> >>>>> "libusb_strerror", but it didn't exist in Linux so I included it  
> >>>>> in hardware.cpp inside #ifdef __WXGTK__, this had to be changed  
> >>>>> in #ifndef __WXMSW__
> >>>>> -The makefile installed /etc/udev/rules.d/26-microchip.rules by  
> >>>>> default. This is a Linux thing only, so it had to be removed for  
> >>>>> osx
> >>>>> -some things in buildmac.sh have been updated to build  
> >>>>> successfully.
> >>>>>
> >>>>> I think it should build now on your system as well!
> >>>>>
> >>>>> Kind regards,
> >>>>>
> >>>>> Frans Schreuder
> >>>>>
> >>>>> On 25-2-2010 17:09, Aleksej Horvat wrote:
> >>>>>> Dear Frans,
> >>>>>>
> >>>>>> Thank you for your continuing support.  Removing the line did  
> >>>>>> clear up the libusb error.  Unfortunately just past that line,  
> >>>>>> I receive many errors relating to wxwidgets, although I also  
> >>>>>> have that installed.  I will look into that, but I am curious  
> >>>>>> what you will find this weekend.  Sorry that I have to ask for  
> >>>>>> this level of support, but configure and make are still a bit  
> >>>>>> of a mystery for me.  I'll keep you informed if I find anything.
> >>>>>>
> >>>>>> Sincerely,
> >>>>>> Aleksej
> >>>>>>
> >>>>>> On 25 feb 2010, at 08:25, Frans Schreuder wrote:
> >>>>>>
> >>>>>>> Dear Aleksej,
> >>>>>>>
> >>>>>>> This weekend, I can borrow a mac from someone, I will try it  
> >>>>>>> myself.
> >>>>>>> It was indeed using some old configuration files, in order to  
> >>>>>>> be able to run from the subversion tree.
> >>>>>>> if you remove the line cp -R osx/* . from configure.sh, this  
> >>>>>>> might help, but I will try further. (you will need to extract  
> >>>>>>> the fresh archive before).
> >>>>>>>
> >>>>>>> Kind regards,
> >>>>>>>
> >>>>>>> Frans Schreuder
> >>>>>>>
> >>>>>>> On 24-2-2010 22:38, Aleksej Horvat wrote:
> >>>>>>>> Dear Frans,
> >>>>>>>>
> >>>>>>>> Thank you for your help.  I was in fact trying to install the  
> >>>>>>>> version 0.3.0.  I have tried following your advice and  
> >>>>>>>> dowloaded the newer branch you mentioned below.   
> >>>>>>>> Unfotunately, the build fails at exactly the same point, even  
> >>>>>>>> though I have libusb 1.0.6 installed.  Perhaps there is  
> >>>>>>>> something outdated in the buildmac.sh file as the error I  
> >>>>>>>> receive still refers to libusb 0.1.x
> >>>>>>>>
> >>>>>>>> Could you please provide some instructions as to how I can  
> >>>>>>>> change this, or perhaps copy libusb to where the script  
> >>>>>>>> expects to find it.  Included below is my terminal outpout.
> >>>>>>>>
> >>>>>>>> Thanks sincerely,
> >>>>>>>> Aleksej
> >>>>>>>>
> >>>>>>>> Renovatio:usbpicprog-823-20100219 ahorvat$ ./buildmac.sh  
> >>>>>>>> make: *** No rule to make target `clean'.  Stop.
> >>>>>>>> checking for a BSD-compatible install... /usr/bin/install -c
> >>>>>>>> checking whether build environment is sane... yes
> >>>>>>>> checking for a thread-safe mkdir -p... ./install-sh -c -d
> >>>>>>>> checking for gawk... no
> >>>>>>>> checking for mawk... no
> >>>>>>>> checking for nawk... no
> >>>>>>>> checking for awk... awk
> >>>>>>>> checking whether make sets $(MAKE)... yes
> >>>>>>>> checking whether to enable maintainer-specific portions of  
> >>>>>>>> Makefiles... no
> >>>>>>>> checking for style of include used by make... GNU
> >>>>>>>> checking for gcc... gcc
> >>>>>>>> checking for C compiler default output file name... a.out
> >>>>>>>> checking whether the C compiler works... yes
> >>>>>>>> checking whether we are cross compiling... no
> >>>>>>>> checking for suffix of executables...
> >>>>>>>> checking for suffix of object files... o
> >>>>>>>> checking whether we are using the GNU C compiler... yes
> >>>>>>>> checking whether gcc accepts -g... yes
> >>>>>>>> checking for gcc option to accept ISO C89... none needed
> >>>>>>>> checking dependency style of gcc... gcc3
> >>>>>>>> checking for library containing strerror... none required
> >>>>>>>> checking for gcc... (cached) gcc
> >>>>>>>> checking whether we are using the GNU C compiler... (cached)  
> >>>>>>>> yes
> >>>>>>>> checking whether gcc accepts -g... (cached) yes
> >>>>>>>> checking for gcc option to accept ISO C89... (cached) none  
> >>>>>>>> needed
> >>>>>>>> checking dependency style of gcc... (cached) gcc3
> >>>>>>>> checking for gcc... (cached) gcc
> >>>>>>>> checking whether we are using the GNU C compiler... (cached)  
> >>>>>>>> yes
> >>>>>>>> checking whether gcc accepts -g... (cached) yes
> >>>>>>>> checking for gcc option to accept ISO C89... (cached) none  
> >>>>>>>> needed
> >>>>>>>> checking dependency style of gcc... (cached) gcc3
> >>>>>>>> checking how to run the C preprocessor... gcc -E
> >>>>>>>> checking for grep that handles long lines and -e... /usr/bin/ 
> >>>>>>>> grep
> >>>>>>>> checking for egrep... /usr/bin/grep -E
> >>>>>>>> checking for ANSI C header files... yes
> >>>>>>>> checking how to run the C preprocessor... gcc -E
> >>>>>>>> checking for g++... g++
> >>>>>>>> checking whether we are using the GNU C++ compiler... yes
> >>>>>>>> checking whether g++ accepts -g... yes
> >>>>>>>> checking dependency style of g++... gcc3
> >>>>>>>> checking build system type... powerpc-apple-darwin9.8.0
> >>>>>>>> checking host system type... powerpc-apple-darwin9.8.0
> >>>>>>>> checking for a sed that does not truncate output... /usr/bin/ 
> >>>>>>>> sed
> >>>>>>>> checking for fgrep... /usr/bin/grep -F
> >>>>>>>> checking for ld used by gcc... /usr/libexec/gcc/powerpc-apple- 
> >>>>>>>> darwin9/4.0.1/ld
> >>>>>>>> checking if the linker (/usr/libexec/gcc/powerpc-apple- 
> >>>>>>>> darwin9/4.0.1/ld) is GNU ld... no
> >>>>>>>> checking for BSD- or MS-compatible name lister (nm)... /usr/ 
> >>>>>>>> bin/nm -p
> >>>>>>>> checking the name lister (/usr/bin/nm -p) interface... BSD nm
> >>>>>>>> checking whether ln -s works... yes
> >>>>>>>> checking the maximum length of command line arguments... 196608
> >>>>>>>> checking whether the shell understands some XSI constructs...  
> >>>>>>>> yes
> >>>>>>>> checking whether the shell understands "+="... yes
> >>>>>>>> checking for /usr/libexec/gcc/powerpc-apple-darwin9/4.0.1/ld  
> >>>>>>>> option to reload object files... -r
> >>>>>>>> checking for objdump... no
> >>>>>>>> checking how to recognize dependent libraries... pass_all
> >>>>>>>> checking for ar... ar
> >>>>>>>> checking for strip... strip
> >>>>>>>> checking for ranlib... ranlib
> >>>>>>>> checking command to parse /usr/bin/nm -p output from gcc  
> >>>>>>>> object... ok
> >>>>>>>> checking for dsymutil... dsymutil
> >>>>>>>> checking for nmedit... nmedit
> >>>>>>>> checking for lipo... lipo
> >>>>>>>> checking for otool... otool
> >>>>>>>> checking for otool64... no
> >>>>>>>> checking for -single_module linker flag... yes
> >>>>>>>> checking for -exported_symbols_list linker flag... yes
> >>>>>>>> checking for sys/types.h... yes
> >>>>>>>> checking for sys/stat.h... yes
> >>>>>>>> checking for stdlib.h... yes
> >>>>>>>> checking for string.h... yes
> >>>>>>>> checking for memory.h... yes
> >>>>>>>> checking for strings.h... yes
> >>>>>>>> checking for inttypes.h... yes
> >>>>>>>> checking for stdint.h... yes
> >>>>>>>> checking for unistd.h... yes
> >>>>>>>> checking for dlfcn.h... yes
> >>>>>>>> checking whether we are using the GNU C++ compiler...  
> >>>>>>>> (cached) yes
> >>>>>>>> checking whether g++ accepts -g... (cached) yes
> >>>>>>>> checking dependency style of g++... (cached) gcc3
> >>>>>>>> checking how to run the C++ preprocessor... g++ -E
> >>>>>>>> checking for objdir... .libs
> >>>>>>>> checking if gcc supports -fno-rtti -fno-exceptions... no
> >>>>>>>> checking for gcc option to produce PIC... -fno-common -DPIC
> >>>>>>>> checking if gcc PIC flag -fno-common -DPIC works... yes
> >>>>>>>> checking if gcc static flag -static works... no
> >>>>>>>> checking if gcc supports -c -o file.o... yes
> >>>>>>>> checking if gcc supports -c -o file.o... (cached) yes
> >>>>>>>> checking whether the gcc linker (/usr/libexec/gcc/powerpc- 
> >>>>>>>> apple-darwin9/4.0.1/ld) supports shared libraries... yes
> >>>>>>>> checking dynamic linker characteristics... darwin9.8.0 dyld
> >>>>>>>> checking how to hardcode library paths into programs...  
> >>>>>>>> immediate
> >>>>>>>> checking whether stripping libraries is possible... yes
> >>>>>>>> checking if libtool supports shared libraries... yes
> >>>>>>>> checking whether to build shared libraries... yes
> >>>>>>>> checking whether to build static libraries... yes
> >>>>>>>> checking for ld used by g++... /usr/libexec/gcc/powerpc-apple- 
> >>>>>>>> darwin9/4.0.1/ld
> >>>>>>>> checking if the linker (/usr/libexec/gcc/powerpc-apple- 
> >>>>>>>> darwin9/4.0.1/ld) is GNU ld... no
> >>>>>>>> checking whether the g++ linker (/usr/libexec/gcc/powerpc- 
> >>>>>>>> apple-darwin9/4.0.1/ld) supports shared libraries... yes
> >>>>>>>> checking for g++ option to produce PIC... -fno-common -DPIC
> >>>>>>>> checking if g++ PIC flag -fno-common -DPIC works... yes
> >>>>>>>> checking if g++ static flag -static works... no
> >>>>>>>> checking if g++ supports -c -o file.o... yes
> >>>>>>>> checking if g++ supports -c -o file.o... (cached) yes
> >>>>>>>> checking whether the g++ linker (/usr/libexec/gcc/powerpc- 
> >>>>>>>> apple-darwin9/4.0.1/ld) supports shared libraries... yes
> >>>>>>>> checking dynamic linker characteristics... darwin9.8.0 dyld
> >>>>>>>> checking how to hardcode library paths into programs...  
> >>>>>>>> immediate
> >>>>>>>> checking locale.h usability... yes
> >>>>>>>> checking locale.h presence... yes
> >>>>>>>> checking for locale.h... yes
> >>>>>>>> checking for LC_MESSAGES... yes
> >>>>>>>> checking libintl.h usability... no
> >>>>>>>> checking libintl.h presence... no
> >>>>>>>> checking for libintl.h... no
> >>>>>>>> checking whether NLS is requested... yes
> >>>>>>>> checking for intltool >= 0.35.0... 0.40.6 found
> >>>>>>>> checking for intltool-update... /opt/local/bin/intltool-update
> >>>>>>>> checking for intltool-merge... /opt/local/bin/intltool-merge
> >>>>>>>> checking for intltool-extract... /opt/local/bin/intltool- 
> >>>>>>>> extract
> >>>>>>>> checking for xgettext... /opt/local/bin/xgettext
> >>>>>>>> checking for msgmerge... /opt/local/bin/msgmerge
> >>>>>>>> checking for msgfmt... /opt/local/bin/msgfmt
> >>>>>>>> checking for gmsgfmt... /opt/local/bin/msgfmt
> >>>>>>>> checking for perl... /opt/local/bin/perl
> >>>>>>>> checking for perl >= 5.8.1... 5.8.9
> >>>>>>>> checking for XML::Parser... ok
> >>>>>>>> checking for wx-config... /usr/local/bin/wx-config
> >>>>>>>> checking for wxWidgets version >= 2.8.0... yes (version 2.9.0)
> >>>>>>>> checking for wxWidgets static library... yes
> >>>>>>>> checking for usb_bulk_write in -lusb... no
> >>>>>>>> configure: error:
> >>>>>>>>     Libusb 0.1.x is required.
> >>>>>>>>
> >>>>>>>>     Please install it from your package manager.
> >>>>>>>>
> >>>>>>>> make: *** No targets specified and no makefile found.  Stop.
> >>>>>>>> make: Nothing to be done for `install'.
> >>>>>>>> cp: src/usbpicprog.app/Contents/MacOS/output/bin/usbpicprog:  
> >>>>>>>> No such file or directory
> >>>>>>>> cp: src/usbpicprog.app/Contents/MacOS/output/lib/locale: No  
> >>>>>>>> such file or directory
> >>>>>>>> cp: libs//libusb.dylib: No such file or directory
> >>>>>>>> otool: can't open file: libs//libusb.dylib (No such file or  
> >>>>>>>> directory)
> >>>>>>>> install_name_tool: can't open file: src/usbpicprog.app/ 
> >>>>>>>> Contents/SharedSupport/libusb.dylib (No such file or directory)
> >>>>>>>> Usage: install_name_tool [-change old new] ... [-id name] input
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On 22 feb 2010, at 08:53, Frans Schreuder wrote:
> >>>>>>>>
> >>>>>>>>> Dear Aleksej,
> >>>>>>>>>
> >>>>>>>>> I am sorry that I have missed your message.
> >>>>>>>>> the forums have been deleted because usbpicprog had too many  
> >>>>>>>>> channels of
> >>>>>>>>> getting support, we have now chosen to use the mailing list
> >>>>>>>>> usb...@li... as the main  
> >>>>>>>>> support channel.
> >>>>>>>>>
> >>>>>>>>> I think the problem you are facing is the version of libusb  
> >>>>>>>>> that
> >>>>>>>>> usbpicprog demands, and this is also related to the version of
> >>>>>>>>> usbpicprog that you are trying to compile.
> >>>>>>>>> I think you have tried to compile version 0.3.0 which needs  
> >>>>>>>>> libusb-0.1.
> >>>>>>>>> However, we recently switched to the newer version of libusb;
> >>>>>>>>> libusb-1.0, this is true for any development branch of  
> >>>>>>>>> usbpicprog > 803.
> >>>>>>>>> I suggest that you try downloading
> >>>>>>>>> http://usbpicprog.org/downloads/ 
> >>>>>>>>> usbpicprog-823-20100219.tar.gz and build
> >>>>>>>>> it.
> >>>>>>>>> You will also need the development version of wxWidgets, 2.9.0
> >>>>>>>>> installed.
> >>>>>>>>>
> >>>>>>>>> Kind regards,
> >>>>>>>>>
> >>>>>>>>> Frans Schreuder
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Sun, 2010-02-21 at 18:41 +0100, Aleksej Horvat wrote:
> >>>>>>>>>> Name: Aleksej Horvat
> >>>>>>>>>>
> >>>>>>>>>> Email: ah...@ma...
> >>>>>>>>>>
> >>>>>>>>>> Subject: Mac OS X PPC Compile
> >>>>>>>>>>
> >>>>>>>>>> Message: Hello,
> >>>>>>>>>> A few days ago I posted a request for advice in the forum on
> >>>>>>>>>> SourceForge. As of now I see that the forum has This leads  
> >>>>>>>>>> me to
> >>>>>>>>>> believe that I won't be receiving any advice.
> >>>>>>>>>> I am running OS X 10.5.8 on PPC Mac, however, I have  
> >>>>>>>>>> attempted the
> >>>>>>>>>> buildmac.sh on an Intel Mac I have access to and it fails  
> >>>>>>>>>> at the same
> >>>>>>>>>> point. I have installed the latest wxwidgets and libusb  
> >>>>>>>>>> (through fink,
> >>>>>>>>>> although that shouldn't matter). The problem is related to  
> >>>>>>>>>> the 'has
> >>>>>>>>>> libusb' check in the makefile, relating to the  
> >>>>>>>>>> usb_bulk_write command.
> >>>>>>>>>> I have checked my installation and I do have libusb in my  
> >>>>>>>>>> path.
> >>>>>>>>>> I have basic programming experience, but I am unfortunately  
> >>>>>>>>>> not
> >>>>>>>>>> terribly familiar with the make syntax at this moment.  
> >>>>>>>>>> Which means I
> >>>>>>>>>> am not able to immediately debug the makefile. Perhaps if  
> >>>>>>>>>> you gave me
> >>>>>>>>>> some advice, I could try and let you know what happens.  
> >>>>>>>>>> Terminal
> >>>>>>>>>> output does not fit the character limit here.
> >>>>>>>>>> Any help would be greatly appreciated,
> >>>>>>>>>> Aleksej
> >>>>>>>>>>
> >>>>>>>>>> IP: 85.146.126.46
> >>>>>>>>>> HOST: s55927e2e.adsl.wanadoo.nl
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
>