On Saturday, 16 February 2019 at 16:28:09 UTC, Ron Tarrant wrote:
On Saturday, 16 February 2019 at 14:29:56 UTC, Russel Winder
wrote:
Pass, sorry.
Thanks for the replies, guys...
I quoted the above line because it's just about the only thing
I understood. Let me explain...
It's been almost 20 years since I used Linux and my notes are
long gone. A ton of things have changed. Like, for instance, it
found all my hardware this time, without me getting involved.
But also the software installation managers and lots of other
things are completely unrecognizable. On top of that, my brain
has (unfortunately) been molded into the Windows/Microsoft way
of thinking.
I guess what I'm hoping for is a step-by-step,
full-on-hand-holding, large-print with pictures tutorial for
how to get GtkD and (I guess) dub working. I know the stuff you
wrote is probably helpful, but I'm not well-enough versed in
Linux or any flavour of UNIX ATM to understand it, pick which
option I should use, and to put these commands in proper order.
So far, as I said, dmd is working. Up until now, I've avoided
dub because, with so many code examples (more than 70 at
present) dub would bring in a lot of file/directory clutter.
But you're saying that dub will make it easier to keep up with
future changes/updates in all the various bits and bobs, so if
that means I finally have to do dub, perhaps someone could
point me at a good tutorial for that?
Sorry if I sound ungrateful or cranky, but I have a lot on my
plate ATM and I'm getting frustrated.
Create a file sample1.d with following content
#!/usr/bin/env dub
/+ dub.sdl:
dependency "vibe-d" version="~>0.8.0"
+/
void main()
{
import vibe.d;
listenHTTP(":8080", (req, res) {
res.writeBody("Hello, World: " ~ req.path);
});
runApplication();
}
Replace the dependency with the gtkd dependency and the main
coding with the gtkd coding.
To start the application you can use one of these commands
dub sample1.d
dub sample1
./sample1
Kind regards
Andre
