• Alex (2/2) Sep 20 2007 I'm currently working on a very simply DLL library, which I'm compiling ...
• Alex (1/1) Sep 20 2007 Sorry, I should added that bud deletes my definition file only when I ru...
• BCS (5/8) Sep 20 2007 I think, rather than use a .def file, you should use the "export " keywo...
• Derek Parnell (8/16) Sep 20 2007 The problem is that it has the same name as the target exe. Try renaming

Alex <CppCoder gmail.com> writes:

I'm currently working on a very simply DLL library, which I'm compiling against
tango by way of the build utility (bud).  I've got a symbol I'm exporting via a
definition file, but whenever I try to compile the app, bud deletes it and does
not export the symbol.  What am I doing wrong?

command line for reference: bud main.d main.def kernel32.lib

Alex <CppCoder gmail.com> writes:

Sorry, I should added that bud deletes my definition file only when I run it
with the -clean directive

BCS <ao pathlink.com> writes:

Reply to alex,

 Sorry, I should added that bud deletes my definition file only when I
 run it with the -clean directive
 

I think, rather than use a .def file, you should use the "export " keyword 
like this

export int fn(){...}

but then I have never created a DLL.

Derek Parnell <derek psych.ward> writes:

On Thu, 20 Sep 2007 16:54:55 -0400, Alex wrote:

 I'm currently working on a very simply DLL library, 
which I'm compiling against tango by way of the build
 utility (bud).  I've got a symbol I'm exporting via
 a definition file, but whenever I try to compile the
 app, bud deletes it and does not export the symbol.
  What am I doing wrong?
 
 command line for reference: bud main.d main.def kernel32.lib

The problem is that it has the same name as the target exe. Try renaming
it.

  bud main.d export.def kernel32.lib

-- 
Derek Parnell
Melbourne, Australia
skype: derek.j.parnell