On Thursday, 18 May 2017 at 18:00:02 UTC, Rainer Schuetze wrote:
That's what I meant with "other cross module dependencies". In
this case it might work if you export
_D10handmade_h10game_input6__initZ from your DLL with the help
of a def-file, but that's not something that scales well.
On 18.05.2017 09:53, Igor wrote:
On Thursday, 18 May 2017 at 07:10:54 UTC, Rainer Schuetze wrote:
You have to add an import path to the folder with dllproj inside to
the project configuration of the exeproject.
If you want to limit the imported code to the declarations, you can
enable
On Thursday, 18 May 2017 at 07:53:02 UTC, Igor wrote:
I tried just adding import paths to project and to di files and
although compilation passes I still get link errors like:
error LNK2019: unresolved external symbol
_D10handmade_h10game_input6__initZ
(handmade_h.game_input.__init)
On Thursday, 18 May 2017 at 07:10:54 UTC, Rainer Schuetze wrote:
You have to add an import path to the folder with dllproj
inside to the project configuration of the exeproject.
If you want to limit the imported code to the declarations, you
can enable "generate interface headers" and add
On Wednesday, 17 May 2017 at 19:48:42 UTC, Igor wrote:
On Wednesday, 17 May 2017 at 18:03:04 UTC, Igor wrote:
What exactly do mean by "binding"?
Also I am wondering if using extern(C) as opposed to extern(D)
only affects name mangling or am I losing some DLang
possibilities since I am only
On 17.05.2017 18:56, Igor wrote:
At the moment I have:
EXEProject:
app.d - it does loadlibrary of dllproj and uses data structures
defined in dllproj.d (it imports dllproj). On the file system this file
is under /platform/win32/ and is defined as module win32.app;
DLLProject
dllproj.d -
On Wednesday, 17 May 2017 at 18:03:04 UTC, Igor wrote:
What exactly do mean by "binding"?
If I understand the rest you are saying that I could just use
"Add existing item" to add the dllproj.d file to EXEProject as
well, but that would cause all of the code from it to be linked
in the EXE
On Wednesday, 17 May 2017 at 17:48:50 UTC, solidstate1991 wrote:
I think you should make a binding for your DLL file. On the
other hand I successfully set up a static library and an
application in the same solution (now it has 2 apps, one is my
map editor and file converter, the other is a
On Wednesday, 17 May 2017 at 16:56:13 UTC, Igor wrote:
At the moment I have:
EXEProject:
app.d - it does loadlibrary of dllproj and uses data
structures defined in dllproj.d (it imports dllproj). On the
file system this file is under /platform/win32/
and is defined as module win32.app;
At the moment I have:
EXEProject:
app.d - it does loadlibrary of dllproj and uses data structures
defined in dllproj.d (it imports dllproj). On the file system
this file is under /platform/win32/ and is defined
as module win32.app;
DLLProject
dllproj.d - exports functions and contains
10 matches
Mail list logo
