On Wednesday, 2 August 2017 at 14:59:39 UTC, Mike Wey wrote:
On 01-08-17 22:50, Johnson Jones wrote:
So, the problem is simple(but unfortunately a lot of wasted
time). gtkD needs to be updated to work well with x64 and x86.
I think all one has to do is be able to specify which path of
gtk
On 01-08-17 22:50, Johnson Jones wrote:
So, the problem is simple(but unfortunately a lot of wasted time). gtkD
needs to be updated to work well with x64 and x86. I think all one has
to do is be able to specify which path of gtk to use rather than have it
search the windows path.
While I
On Tuesday, 1 August 2017 at 21:03:44 UTC, Mike Wey wrote:
On 01-08-17 22:16, Johnson Jones wrote:
nvm, the file exists. Why it is not being found is unknown.
I did some stuff and it says it is not a valid win32, this is
using that gtk3 runtime I linked to... says it's x64 version
but
On 01-08-17 22:16, Johnson Jones wrote:
nvm, the file exists. Why it is not being found is unknown.
I did some stuff and it says it is not a valid win32, this is using that
gtk3 runtime I linked to... says it's x64 version but probably x86.
Would be nice if the error message printed the
So, The error I currently get is
object.Exception@generated\gtkd\gtkd\Loader.d(125): Library load
failed (libgdk-3-0x64.dll): is not a valid Win32 application.
and libgdk-3-0x64.dll was libgdk-3-0.dll from the 64-bit gtk
package. (I simply added the extension)... the package downloaded
nvm, the file exists. Why it is not being found is unknown.
I did some stuff and it says it is not a valid win32, this is
using that gtk3 runtime I linked to... says it's x64 version but
probably x86.
Would be nice if the error message printed the full path of what
was being loaded so it's
On Tuesday, 1 August 2017 at 15:14:50 UTC, Mike Wey wrote:
On 01-08-17 01:37, Johnson Jones wrote:
So, the question is, is this a gtkd problem or a gtk problem?
In either case, what's the way to get them both to work. Do
you guys actually test out both versions installed on the same
system?
On 01-08-17 01:37, Johnson Jones wrote:
So, the question is, is this a gtkd problem or a gtk problem? In either
case, what's the way to get them both to work. Do you guys actually test
out both versions installed on the same system?
Gtk also loads some of it's own libraries at start up
On Monday, 31 July 2017 at 20:37:11 UTC, Mike Wey wrote:
On 31-07-17 19:16, Johnson Jones wrote:
how does one allow both gtk x86 and x64 to work side by side
seamlessly?
I installed x64 first and it seems, because whatever is using
the path to find the gtk runtime, it looks for that first
On 31-07-17 19:53, Johnson Jones wrote:
Also, why is gtkD even using gtksharp? That's for mono and .net!
We don't. only the (C) Gtk runtime is needed.
Where did you see gtksharp?
--
Mike Wey
On 31-07-17 19:16, Johnson Jones wrote:
how does one allow both gtk x86 and x64 to work side by side seamlessly?
I installed x64 first and it seems, because whatever is using the path
to find the gtk runtime, it looks for that first even in x86 build.
Seems like gtkd's dll resolution is not
On Monday, 31 July 2017 at 17:50:08 UTC, Johnson Jones wrote:
On Monday, 31 July 2017 at 17:16:32 UTC, Johnson Jones wrote:
[...]
I fixed up gtkd so that it uses x86 and x64 versions of dlls
but it doesn't seem to help with x64. I was able to get x86 to
compile and run but x64 just loads
On Monday, 31 July 2017 at 17:16:32 UTC, Johnson Jones wrote:
how does one allow both gtk x86 and x64 to work side by side
seamlessly?
I installed x64 first and it seems, because whatever is using
the path to find the gtk runtime, it looks for that first even
in x86 build.
Seems like
13 matches
Mail list logo
