On Thursday, 3 August 2017 at 21:00:17 UTC, Mike Wey wrote:
On 03-08-17 22:40, Johnson Jones wrote:
Ok, so, I linked the gtk to the msys gtk that I installed
before when trying to get glade to work and it worked!
seems that msys is much more up to date than anything else as
it just works(I need to remember than in the future).
The problem I see is this:
When I get ready to release my app to the public, I can't
expect them to all have to install msys and build.
msys seems to clump everything together and I don't know what
files I need to extract to be able to bundle everything
together.
Any ideas how to solve that problem? At least now I can move
ahead and actually make some progress on my app.
Would still be nice to get the x86 vs x64 issue resolved so I
don't have to keep switching between the two for testing
purposes. Since Visual D was just patched to handle x64 BP's I
guess I can stay with that for now.
I'll try to build and test some new installers tomorrow that
will include the loaders.
Thanks. Could you take a look at the loading image thread I
started when you get time? I can't seem to get an image to load
even though it seems straight forward.
These are the pixbufs I'm using
mingw32/mingw-w64-i686-gdk-pixbuf2 2.36.6-2 [installed]
An image loading library (mingw-w64)
mingw64/mingw-w64-x86_64-gdk-pixbuf2 2.36.6-2 [installed]
An image loading library (mingw-w64)
in x64 it crashes completely without an exception though... which
is why I want an easy way to switch between the two
architectures... since x64 seems to be more unstable than x86 but
sometimes it's the reverse, and ultimately I'll want to release
in x64.
Also, do I ever need to rebuild gdk when changing gtk
installations? Does it ever grab anything from them at compile
time or is it all at runtime?
