You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way to create dynlibs with DMD is to pass a .def along with source files in the command-line.
For now, I must use
"sourceFiles": [
"./main.d",
"./main.def"
],
else no symbol is exported.
But then every other source file must be provided manually. A solution would be that .def files found in sourcePaths be added to the list of source files.
The text was updated successfully, but these errors were encountered:
p0nce
changed the title
DUB could include .def files in source Files by itself
DUB could include .def files in sourcePaths instead of just .d
May 26, 2015
"sourceFiles" are additive w.r.t "sourcePaths", so you can still use that, or you could use a glob expression within "sourceFiles" to include multiple files at once.
The way to create dynlibs with DMD is to pass a .def along with source files in the command-line.
For now, I must use
else no symbol is exported.
But then every other source file must be provided manually. A solution would be that .def files found in
sourcePathsbe added to the list of source files.The text was updated successfully, but these errors were encountered: