August 03, 2017
On 03-08-17 05:00, Johnson Jones wrote:
> On Wednesday, 2 August 2017 at 14:51:45 UTC, Mike Wey wrote:
>> On 02-08-17 08:04, Johnson Jones wrote:
>>> Ok, Using msys I was able to get glade 3.20 running. Maybe that will fix everything.
>>
>> Great, unfortunately "Use msys2" seems to be the official way to install anything GTK related on windows.
> 
> ... Also, I cannot seem to load a jpg using an imageview
> 
> (test.exe:1628): Gtk-WARNING **: Could not load image 'a.jpg': Couldn't recognize the image file format for file 'a.jpg'
> 
> Just a normal jpg. Tried a bmp, same thing. It shows fine in glade itself.
> 

It looks like the pixbuf loaders are missing from the installer.

-- 
Mike Wey
August 03, 2017
On Thursday, 3 August 2017 at 15:11:46 UTC, Mike Wey wrote:
> On 03-08-17 05:00, Johnson Jones wrote:
>> On Wednesday, 2 August 2017 at 14:51:45 UTC, Mike Wey wrote:
>>> On 02-08-17 08:04, Johnson Jones wrote:
>>>> Ok, Using msys I was able to get glade 3.20 running. Maybe that will fix everything.
>>>
>>> Great, unfortunately "Use msys2" seems to be the official way to install anything GTK related on windows.
>> 
>> ... Also, I cannot seem to load a jpg using an imageview
>> 
>> (test.exe:1628): Gtk-WARNING **: Could not load image 'a.jpg': Couldn't recognize the image file format for file 'a.jpg'
>> 
>> Just a normal jpg. Tried a bmp, same thing. It shows fine in glade itself.
>> 
>
> It looks like the pixbuf loaders are missing from the installer.

How do I remedy this?
August 03, 2017
On Thursday, 3 August 2017 at 15:11:46 UTC, Mike Wey wrote:
> On 03-08-17 05:00, Johnson Jones wrote:
>> On Wednesday, 2 August 2017 at 14:51:45 UTC, Mike Wey wrote:
>>> On 02-08-17 08:04, Johnson Jones wrote:
>>>> Ok, Using msys I was able to get glade 3.20 running. Maybe that will fix everything.
>>>
>>> Great, unfortunately "Use msys2" seems to be the official way to install anything GTK related on windows.
>> 
>> ... Also, I cannot seem to load a jpg using an imageview
>> 
>> (test.exe:1628): Gtk-WARNING **: Could not load image 'a.jpg': Couldn't recognize the image file format for file 'a.jpg'
>> 
>> Just a normal jpg. Tried a bmp, same thing. It shows fine in glade itself.
>> 
>
> It looks like the pixbuf loaders are missing from the installer.

I tried to use the mingw version of gtk with no luck. It first looks in C:\MinGW even though I have MinGW installed somewhere else. Using a junction doesn't help becomes then it when it finds the dll it has missing symbols

"The Procedure Entry Point gdk_pixbuf_gettext could not be located in the dynamic link library C:\MinGW\lib\gdk-pix-buf-2.0\2.10.0\loaders\libpixbufloader-gdip-jpeg.dll".

I actually just copied over the loaders rather than using the full gtk mingw install because when I do that it complains about some lib??svg missing. I guess one can't mix mingw installs with non-mingw... but the gtk mingw install is incomplete too ;/

I hope this isn't going to be an on going thing... seems I've wasted quite a bit of time to try and get gdk to work. I probably could have written my own gui by now.
August 03, 2017
On Thursday, 3 August 2017 at 15:11:46 UTC, Mike Wey wrote:
> On 03-08-17 05:00, Johnson Jones wrote:
>> On Wednesday, 2 August 2017 at 14:51:45 UTC, Mike Wey wrote:
>>> On 02-08-17 08:04, Johnson Jones wrote:
>>>> Ok, Using msys I was able to get glade 3.20 running. Maybe that will fix everything.
>>>
>>> Great, unfortunately "Use msys2" seems to be the official way to install anything GTK related on windows.
>> 
>> ... Also, I cannot seem to load a jpg using an imageview
>> 
>> (test.exe:1628): Gtk-WARNING **: Could not load image 'a.jpg': Couldn't recognize the image file format for file 'a.jpg'
>> 
>> Just a normal jpg. Tried a bmp, same thing. It shows fine in glade itself.
>> 
>
> It looks like the pixbuf loaders are missing from the installer.

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.



August 03, 2017
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.

-- 
Mike Wey
August 03, 2017
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?









August 05, 2017
On 03-08-17 23:11, Johnson Jones wrote:
> 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?

The new installers are available: https://gtkd.org/Downloads/runtime/

You don't need to rebuild GtkD when changing GTK installations, it does it all at runtime.

-- 
Mike Wey
1 2
Next ›   Last »