multiple windows dlls results in "entry point could not be located" depending on order

2021-05-27 Thread cartland via Digitalmars-d-learn
I have built 2 windows C dlls (ctst and ctst2) that I am calling from a Dlang exe (dtstx). dumpbin shows the exports. dpp was used to generate the d file from #includes. All this works perfectly on Linux and MacOS. (Are the generated d files portable? They seem to be. I have also generated th

Re: Exceptions on Windows being "swallowed"

2019-11-26 Thread cartland via Digitalmars-d-learn
On Wednesday, 27 November 2019 at 05:43:33 UTC, Mike Parker wrote: On Wednesday, 27 November 2019 at 05:15:10 UTC, cartland wrote: *snip* dmd -m32mscoff -debug -g x.d And see what happens. No difference between "dmd -m32mscoff -debug -g x.d" and "dmd -m32mscoff x.d" C:\tmp\x>dmd -

Re: Exceptions on Windows being "swallowed"

2019-11-26 Thread cartland via Digitalmars-d-learn
This works (once I installed Microsoft Visual C++ 2010 x64 Redistributable) : dub --force -v Seems the issue is with "x86_mscoff" -- : Performing "debug" build using C:\D\dmd2\windows\bin\dmd.exe for x86_64. x ~master: building configuration "application"... C:\D\dmd2\windows\bi

Re: Exceptions on Windows being "swallowed"

2019-11-26 Thread cartland via Digitalmars-d-learn
On Wednesday, 27 November 2019 at 04:11:44 UTC, Mike Parker wrote: On Wednesday, 27 November 2019 at 02:48:53 UTC, cartland wrote: Trying out exception handling. When an exception occurs, program seems to just exit. dub -a x86_mscoff I compiled it with dmd and ran it directly from the comma

Exceptions on Windows being "swallowed"

2019-11-26 Thread cartland via Digitalmars-d-learn
Trying out exception handling. When an exception occurs, program seems to just exit. dub -a x86_mscoff Performing "debug" build using C:\D\dmd2\windows\bin\dmd.exe for x86, x86_mscoff. x ~master: target for configuration "application" is up to date. To force a rebuild of up-to-date targets, r

(SOLVED) Re: linking to shared lib on Windows

2019-11-19 Thread cartland via Digitalmars-d-learn
On Wednesday, 13 November 2019 at 00:47:11 UTC, cartland wrote: I now have the following working on Linux and macOS. *snip* What is the approach on Windows these days (many posts on the matter seem out of date)? The shared C dll was built in MSYS2/MINGW32. *snip* FYI Got it working using t

Re: (SOLVED) Re: linking to shared lib on Windows

2019-11-19 Thread cartland via Digitalmars-d-learn
On Tuesday, 19 November 2019 at 10:10:14 UTC, cartland wrote: On Wednesday, 13 November 2019 at 00:47:11 UTC, cartland wrote: *snip* PS I uninstalled ALL Microsoft build tools and Visual Studios, then reinstalled DMD and LDC.

linking to shared lib on Windows

2019-11-12 Thread cartland via Digitalmars-d-learn
I now have the following working on Linux and macOS. - name "myapp" targetType "executable" description "A minimal D application." authors "bartland" copyright "Copyright © 2019, bartland" license "public" libs "mylib" lflags "-L../../_cache/" "-rpath" "../../_cache/" --- What is the app

(SOLVED) Re: rpath on macOS

2019-11-12 Thread cartland via Digitalmars-d-learn
On Tuesday, 12 November 2019 at 10:44:07 UTC, kinke wrote: On Tuesday, 12 November 2019 at 10:19:30 UTC, cartland wrote: but on macOS with DMD or LDC this gives ld: unknown option: -rpath=../../_cache/" IIRC, Mac's ld64 linker requires 2 separated args: "-rpath" "..

Re: rpath on macOS

2019-11-12 Thread cartland via Digitalmars-d-learn
On Tuesday, 12 November 2019 at 10:19:30 UTC, cartland wrote: On Linux, this works: *snip* but on macOS with DMD or LDC this gives ld: unknown option: -rpath=../../_cache/" Currently I do this post build to get the binary to work: -- install_na

rpath on macOS

2019-11-12 Thread cartland via Digitalmars-d-learn
On Linux, this works: name "myapp" targetType "executable" description "A minimal D application." authors "bartland" copyright "Copyright © 2019, bartland" license "public" libs "mylib" lflags "-L../../_cache/" "-rpath=../../_cache/" but on macOS with DMD or LDC this gi

Re: (SOLVED) requests module generates " Can't parse uri '' "

2019-11-09 Thread cartland via Digitalmars-d-learn
On Sunday, 10 November 2019 at 01:28:13 UTC, cartland wrote: On Saturday, 9 November 2019 at 01:02:57 UTC, cartland wrote: On Saturday, 9 November 2019 at 00:53:13 UTC, cartland wrote: On Friday, 8 November 2019 at 17:01:07 UTC, ikod wrote: *snip* Even this does it. import requests; void main(

Re: (SOLVED) requests module generates " Can't parse uri '' "

2019-11-09 Thread cartland via Digitalmars-d-learn
On Saturday, 9 November 2019 at 01:02:57 UTC, cartland wrote: On Saturday, 9 November 2019 at 00:53:13 UTC, cartland wrote: On Friday, 8 November 2019 at 17:01:07 UTC, ikod wrote: *snip* Even this does it. import requests; void main() { } https://github.com/ikod/dlang-requests/issues/109 Fi

Re: requests module generates " Can't parse uri '' "

2019-11-08 Thread cartland via Digitalmars-d-learn
On Saturday, 9 November 2019 at 00:53:13 UTC, cartland wrote: On Friday, 8 November 2019 at 17:01:07 UTC, ikod wrote: *snip* Even this does it. import requests; void main() { } https://github.com/ikod/dlang-requests/issues/109

Re: requests module generates " Can't parse uri '' "

2019-11-08 Thread cartland via Digitalmars-d-learn
On Friday, 8 November 2019 at 17:01:07 UTC, ikod wrote: On Friday, 8 November 2019 at 03:29:41 UTC, cartland wrote: First time D use :) After dub init, I used the example from https://code.dlang.org/packages/requests and ran "dub add requests" [...] If you still stuck with this problem, y

Re: requests module generates " Can't parse uri '' "

2019-11-07 Thread cartland via Digitalmars-d-learn
On Friday, 8 November 2019 at 03:43:52 UTC, Adam D. Ruppe wrote: On Friday, 8 November 2019 at 03:36:22 UTC, cartland wrote: * snip * huh, idk, it works when I try that exact code in a fresh project * snip * are you behind a proxy or something maybe? Thanks for checking. I'm not behind a p

Re: requests module generates " Can't parse uri '' "

2019-11-07 Thread cartland via Digitalmars-d-learn
On Friday, 8 November 2019 at 03:31:56 UTC, Adam D. Ruppe wrote: On Friday, 8 November 2019 at 03:29:41 UTC, cartland wrote: When I run dub, I get What was your main() code? The error makes me think you might have just tried like get("") or something import std.stdio; import requests; voi

requests module generates " Can't parse uri '' "

2019-11-07 Thread cartland via Digitalmars-d-learn
First time D use :) After dub init, I used the example from https://code.dlang.org/packages/requests and ran "dub add requests" When I run dub, I get requests.uri.UriException@/home/cartland/.dub/packages/requests-1.0.9/requests/source/requests/uri.d(35): Can't parse uri '' Full output on