On Fri, 09 Jan 2009, Barry Jackson wrote: Hi Barry,
> I have now built my small Linux application using xhgtk front end and > hbtpathy for the com functions - > it works fine - just like my Xbase++ version in Windows - I am really > impressed with Harbour! > It also builds with > hbmk hdvr -lhbtpathy -xhgtk //Much easier than my 3 step approach! > It produces a 40kB executable which runs on this machine. > Question, what other files do I need to deploy to another machine that has > no Harbour installed to enable it to run there? Is there a tool to do this? Such executable file uses shared harbour.so and xhgtk.so libraries and you should install them on destination machine. If you are using RPM based distribution then I suggest to create RPMs for Harbour and XHGTK and then install xhgtk-*.<arch>.rpm and harbour-lib-*.<arch>.rpm. Both contains above shared libraries. You can also create static binaries using -static hb* script parameters. In such case the Harbour and xHarbour libraries will be linked with your application. Anyhow still other system and GTK libraries will be linked dynamically so you will need compatible libraries installed in destination system. You can also use -fullstatic parameter which eliminates this problem and create fully static binaries if you have static version of used libraries installed. Unfortunately GTK does not provide static libs so in this case it will not work. Also static binaries using some system functionality may not be well portable. If you want to reduce the problem with coping binaries between systems then the easiest way is creating shared binaries as you have now and distribute them with used shared libraries (harbour.so and xhgtk.so in this case). Your compiled .prg code or .c code using Harbour API should not have any other external references so even if harbour.so and/or xhgtk.so cannot be installed on destination system then it will be enough to download valid binary libraries for this system or rebuild them from source code without touching your application. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
