Hi all,
I'm building and installing GST in all my machines. I have OSX, Slackware and Windows. In Linux, the build was like a charm. All ok, and VisualGST working without troubles. In OSX, thanks to recent instructions from Paolo builds ok too (in 32 bits), and once I open remote connection for Paolo, I hope soon in 64 bits, and now, I'm looking to get GTK working too. In windows, is a pain. I think I'm getting closer, and I suppose I will get builded soon, but I know GTK will not work. I installed Cygwin, but, I don't know why, a simple ./configure takes a lot to print only one line of what he's doing, and now, I'm fighting to get MinGW/MSys with some troubles too. When I wrote Windows Build guide. For this, I would like to ask one question. For GST builded against GTK, what is needed exactly? Could be enough, to get GTK binaries for Windows, and link to them with some option in configure? I need to build GTK from MinGW? Cheers. _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
On 10/04/2010 06:54 PM, Giuseppe Luigi Punzi wrote:
> For this, I would like to ask one question. > For GST builded against GTK, what is needed exactly? Could be enough, to get > GTK binaries for Windows, and link to them with some option in configure? I > need to build GTK from MinGW? Fedora's cross-compilation environment includes mingw binaries of GTK. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
On 10/05/2010 11:02 AM, Giuseppe Luigi Punzi Ruiz wrote:
> I know, but I use slackware, and I would like to not depend on a > linux box,I would like to build directly from windows Then please do not complain every time about the slowness of configure scripts. It's that way on Windows because of the performance problems of "fork". Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
...?
I'm not complaining about anything. I only said, about slowness in Cygwin, but is a problem of Cygwin not a problem with GST. I asked one thing, you reply me something totally different about what I asked (I appreciate your answer anyway), and I asked about what you wrote. I only asked about what's really needed to build GST with GTK support under Windows, to avoid if possible to build GTK entirely, not about how "easy" is to get Windows binaries from Linux. My intention is to get binaries in all platforms to rewrite Building Guides (obsoletes), to bring an easy way for everyone to get GST working. Because right now, build GST outside Linux, and, especially in Windows, is a pain, but I'm not telling is a fault of GST. Because I'm not a MinGW-Msys/Cywin/Console expert, I ask for help with things I don't understand. I did'nt know, this could be a problem here, sorry for thath. Quoting Paolo Bonzini <[hidden email]>: > On 10/05/2010 11:02 AM, Giuseppe Luigi Punzi Ruiz wrote: >> I know, but I use slackware, and I would like to not depend on a >> linux box,I would like to build directly from windows > > Then please do not complain every time about the slowness of configure > scripts. It's that way on Windows because of the performance problems > of "fork". > > Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
I'm sorry if my answer came out a bit ugly.
The point is, the right thing to do is to provide binary builds, and possibly do that in an automated way. And in order to do it in an automated way, the easiest thing to do is to cross-compile (also because the images can be treated as mostly architecture independent). It's in theory possible to cross-compile for Mac as well. Also, compiling everything is cumbersome as you experienced yourself. This can be made easier by relying on prepackaging done by someone else. This doesn't necessarily point to cross-compiling, but again cross-compilation does take care of that. Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Well, I apologize for my last mail.
I don't read quite well english, and I can understand it in other way as expressed. I have a bad day at work, and is not fault of anybody other than me. Sorry to you and the list, and as always, thanks for your time and efforts. Quoting Paolo Bonzini <[hidden email]>: > I'm sorry if my answer came out a bit ugly. > > The point is, the right thing to do is to provide binary builds, and > possibly do that in an automated way. And in order to do it in an > automated way, the easiest thing to do is to cross-compile (also > because the images can be treated as mostly architecture independent). > It's in theory possible to cross-compile for Mac as well. > > Also, compiling everything is cumbersome as you experienced yourself. > This can be made easier by relying on prepackaging done by someone > else. This doesn't necessarily point to cross-compiling, but again > cross-compilation does take care of that. > > Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Free forum by Nabble | Edit this page |