FW: Dillo project Cross-platform build problem re: GTK
Hi Jorge,
I was wondering if you or someone else familiar with the project might be interested and possibly able to help with a problem that I am faced with in building Dillo. I have a full development environment on an x86 machine and am building there for a remote system which uses an AMD Alchemy MIPS microprocessor. As such, what happens is all the code compiles successfully, but when the time comes to link it all together it runs into problems with GTK. Looking over the
Hello, all - Per Jorge's suggestion, I'm forwarding this message to the group. Perhaps someone here has already done some work on the AMD Alchemy MIPS microprocessor with the Dillo browser(?) Please see my original message below for a description of the problem I am faced with. I will pre-emptively respond with "Unfortunately, no!" to the question of whether or not I can just do the build on the MIPS machine. The reason is that that is a terribly small (poor CPU, low RAM, Flash Disk) machine incapable of supporting the development tools. My current approach is to try and trick the configure script by making it bring up a shell script that I write called "gtk-config" which I will point to in the $PATH environment variable. The output of it will respong to the three queries --cflags, --version and --libs with the responses pertinent to the MIPS target environment while at the same time being executable on the local development environment. Hopefully that'll be sufficient to get it to link everything together successfully. Would appreciate any feedback - I'll post again if the above method is met with any success. Thanks! - Sean -----Original Message----- From: Jorge Arellano Cid [mailto:jcid@softhome.net] Sent: Tuesday, July 01, 2003 5:43 PM To: Sean Kelly Subject: Re: Dillo project Cross-platform build problem re: GTK Sean, project's
default configure file, I see that it attempts to execute the gtk-config program - but this is impossible if the target system is not the same architecture as the development system! The development system has GTK on it, but that's for X86 and cannot be linked in. The target GTK library (libgtk.so) is on the development system as well, but of course cannot be executed because the target processor is different.
Since you mention on your project homepage that Dillo aims to be a multi-platform browser, my hope is that you've by now encountered such a situation. Can you offer any friendly advice or do you know of a simple, straight-forward work-around to this problem? It'd be much appreciated, and I'd certainly be willing to contribute to the project with bug-fixes, compatability testing on the MIPS architecture and such.
Thanks in advance!
I don't remember, but it seems someone posted something about cross-compiling sometime ago. Please send this same mail to our mailing list so everyone there can read it, and hopefully answer. Cheers Jorge.-
Hi, <cross-compiling and GTK>
My current approach is to try and trick the configure script by making it bring up a shell script that I write called "gtk-config" which I will point to in the $PATH environment variable. The output of it will respong to the three queries --cflags, --version and --libs with the responses pertinent to the MIPS target environment while at the same time being executable on the local development environment.
Hmmm, gtk-config is a shell script already - at least on my machine. If you set a variable GTK_CONFIG to point to the MIPS version, ./configure should pick it up and the MIPS version should tell the correct flags. That of course requires that the MIPS gtk-config shell script works correctly. Is the first line #!/bin/sh ? Sometimes these things are set to non-standard shells. And the PATHS in the MIPS gtk-config have to point to the MIPS paths. If everything else fails and you can link other GTK programs, I would simply try the attached patch and addtionally make sure that all GTK stuff gets found. (e.g. setting CPPFLAGS to find the includes and LDFLAGS to find the libs). This is not very clean, though. And in theory the first approach *should* work. Hope that helps, Cheers Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198
Hello Andreas, et al, Thank you for the tip! As it turns out this was a solid lead. I was not aware that gtk-config was just a shell script, so indeed all I had to do was locate the one for the MIPS build of GTK and yeehaw: successful link! Hopefully I can get it installed and running shortly here (having lame problems connecting to the target device presently) and will have some feedback on how this lightweight browser performs on a truly lightweight platform, just as it was designed to do. Regards, - Sean -----Original Message----- From: dillo-dev-admin@auriga.wearlab.de [mailto:dillo-dev-admin@auriga.wearlab.de] On Behalf Of Andreas Schweitzer Sent: Wednesday, July 02, 2003 2:24 AM To: Sean Kelly; dillo-dev@auriga.wearlab.de Subject: Re: [Dillo-dev] FW: Dillo project Cross-platform build problem re: GTK Hi, <cross-compiling and GTK>
My current approach is to try and trick the configure script by making it bring up a shell script that I write called "gtk-config" which I will point to in the $PATH environment variable. The output of it will respong to the three queries --cflags, --version and --libs with the responses pertinent to the MIPS target environment while at the same time being executable on the local development environment.
Hmmm, gtk-config is a shell script already - at least on my machine. If you set a variable GTK_CONFIG to point to the MIPS version, ./configure should pick it up and the MIPS version should tell the correct flags. That of course requires that the MIPS gtk-config shell script works correctly. Is the first line #!/bin/sh ? Sometimes these things are set to non-standard shells. And the PATHS in the MIPS gtk-config have to point to the MIPS paths. If everything else fails and you can link other GTK programs, I would simply try the attached patch and addtionally make sure that all GTK stuff gets found. (e.g. setting CPPFLAGS to find the includes and LDFLAGS to find the libs). This is not very clean, though. And in theory the first approach *should* work. Hope that helps, Cheers Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198
participants (2)
-
Andreas Schweitzer -
Sean Kelly