echo LIBRARY $(TargetFileName) > “$(IntDir)$(TargetName).def”
echo EXPORTS >> “$(IntDir)$(TargetName).def”
echo main >> “$(IntDir)$(TargetName).def”

Then $(IntDir)$(TargetName).def is the .def file needed.

>
> I’m trying to make copying a project and creating a new project as simple
> as possible with as few changes as possible. So far I’ve got my solution
> name passed down to name everything. Except of course the .def file. So I
> made this prebuild script and added it to the project properties:
>
>
Hi Martin,

You don’t need to use def files at all. For Windows put
__declspec(dllexport) in front of your main function. Typically you’d want
to put this in a macro which has its definition depending on the platform,
so for OSX it would be empty, and for Windows it is set to
__declspec(dllexport).

To create a new project from an existing one, I delete everything except the
vcproj file, the solution and the sources. Then I rename the source files,
and open vcproj in a text editor to do a find/replace on the old object
name. All that’s left to do then is some find/replace operations on the
copied source files. You can keep the Max dependencies in the same relative
path to your project directory so the includes don’t need any changes.

I’m sure you can all automate this find/replace business. I’ve been too lazy
to look into it, but if someone figures it out it would be nice to know how
it’s done.

Thijs

dllmain_win.c

?

>
> So, do we really need
>
> dllmain_win.c
>

I’m not sure, but all of my externals so far seem to have been fine without
it. Maybe its obsolete now?

Thijs

Rob