www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - GtkD on Windows: notes + question

reply mark <mark qtrac.eu> writes:
I found a much easier way to get GtkD working on windows than 
that described in 
https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html

1. I downloaded and installed the Gtk3 runtime (the link is on 
https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html)

2. I downloaded and unzipped the GtkD3 zip to C:\bin\GtkD3

3. Since I'd already installed LDC I just had to run:

     dub add-path C:\bin\GtkD3

Now I'm able to build and run on windows using dub. And again, I 
get static builds so have deployable .exes.

However, when I double-click a GtkD .exe it pops up a console 
window, then the GUI window, and the console window stays until I 
close the GUI.

Is there a way to avoid the console Window, at least for release 
builds?
Feb 09 2020
next sibling parent JN <666total wp.pl> writes:
On Sunday, 9 February 2020 at 13:28:59 UTC, mark wrote:

 I found a much easier way to get GtkD working on windows than 
 that described in 
 https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html

 1. I downloaded and installed the Gtk3 runtime (the link is on 
 https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html)

 2. I downloaded and unzipped the GtkD3 zip to C:\bin\GtkD3

 3. Since I'd already installed LDC I just had to run:

     dub add-path C:\bin\GtkD3

 Now I'm able to build and run on windows using dub. And again, 
 I get static builds so have deployable .exes.

 However, when I double-click a GtkD .exe it pops up a console 
 window, then the GUI window, and the console window stays until 
 I close the GUI.

 Is there a way to avoid the console Window, at least for 
 release builds?


https://forum.dlang.org/thread/xkvdpdsfzevanucrgkud forum.dlang.org
Feb 09 2020
prev sibling next sibling parent reply Daniel Kozak <kozzi11 gmail.com> writes:
"lflags-windows": ["/SUBSYSTEM:WINDOWS", "/ENTRY:mainCRTStartup"],

On Sun, Feb 9, 2020 at 2:30 PM mark via Digitalmars-d-learn
<digitalmars-d-learn puremagic.com> wrote:

 I found a much easier way to get GtkD working on windows than
 that described in
 https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html

 1. I downloaded and installed the Gtk3 runtime (the link is on
 https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html)

 2. I downloaded and unzipped the GtkD3 zip to C:\bin\GtkD3

 3. Since I'd already installed LDC I just had to run:

      dub add-path C:\bin\GtkD3

 Now I'm able to build and run on windows using dub. And again, I
 get static builds so have deployable .exes.

 However, when I double-click a GtkD .exe it pops up a console
 window, then the GUI window, and the console window stays until I
 close the GUI.

 Is there a way to avoid the console Window, at least for release
 builds?
Feb 09 2020
next sibling parent mark <mark qtrac.eu> writes:
On Sunday, 9 February 2020 at 14:08:02 UTC, Daniel Kozak wrote:

 "lflags-windows": ["/SUBSYSTEM:WINDOWS", 
 "/ENTRY:mainCRTStartup"],


[snip]

 Is there a way to avoid the console Window, at least for 
 release builds?





Thank you! Your solution I guess is for dub.json.

For those using dub.sdl the necessary line is:

lflags "/SUBSYSTEM:WINDOWS" "/ENTRY:mainCRTStartup" 
platform="windows"
Feb 10 2020
prev sibling parent mark <mark qtrac.eu> writes:
On Sunday, 9 February 2020 at 14:08:02 UTC, Daniel Kozak wrote:

 "lflags-windows": ["/SUBSYSTEM:WINDOWS", 
 "/ENTRY:mainCRTStartup"],


[snip]

 Is there a way to avoid the console Window, at least for 
 release builds?





Thank you! Your solution I guess is for dub.json.

For those using dub.sdl the necessary line is:

lflags "/SUBSYSTEM:WINDOWS" "/ENTRY:mainCRTStartup" 
platform="windows"
Feb 10 2020
prev sibling parent reply Ron Tarrant <rontarrant gmail.com> writes:
On Sunday, 9 February 2020 at 13:28:59 UTC, mark wrote:

 I found a much easier way to get GtkD working on windows than 
 that described in 
 https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html


Just FYI...

I don't use dub because I don't have time to understand its 
foibles well enough to steer new D coders through the maze. 
Besides that, using tools like dub separates one from the process.

Up to you, though, of course.
Feb 11 2020
parent mark <mark qtrac.eu> writes:
On Tuesday, 11 February 2020 at 20:49:40 UTC, Ron Tarrant wrote:

 On Sunday, 9 February 2020 at 13:28:59 UTC, mark wrote:

 I found a much easier way to get GtkD working on windows than 
 that described in 
 https://gtkdcoding.com/2019/01/11/0000-introduction-to-gtkDcoding.html


 Just FYI...

 I don't use dub because I don't have time to understand its 
 foibles well enough to steer new D coders through the maze. 
 Besides that, using tools like dub separates one from the 
 process.

 Up to you, though, of course.


That's understandable. Anyway, once I get back to learning GtkD 
I'll be starting with your blog.
Feb 11 2020