Ryzom

Instead of compiling all with dynamic CRT, could you try to compile all with static CRT ?

I noticed you removed all NL_STATIC parts , but new Release and Debug configurations are static by default now, so you should keep static parts and remove dynamic ones.

For the .rc problem, object_viewer is adding MFC dependencies to 3dsmax plugin, do you think it is worth linking them together ? if I remember, it's just a shortcut to launch it.

.rc can't be linked in a .lib but they can be linked in a .exe :p

I didn't remove anything. The only thing I removed was an ugly hack to link the object_viewer statically to the object_viewer_exe, which I added about a year ago, but this DOES NOT WORK with 3dsmax plugins; because MFC things have a DllMain provided by MFC, and the max plugins provide their own DllMain entry point. It is not possible to link object_viewer statically to nel_export.

Additionally, all plugins are basically a dll on itself, and they share data, which is a scenario which should not and cannot be done with static crt. Compiling with dynamic crt works just fine. Pushing all plugins into one file is NOT a good idea either, btw.

In any case, I don't see a need for static CRT in non-FINAL_VERSION builds. You'll need a seperate config to compile with FINAL_VERSION flag anyway, so you could just as well do static crt only in FINAL_VERSION, since the only scenario where it makes sense, is when sending your app to end users.

There's also the nel_3dsmax_shared dll, which must be a dll in any case, because it is used to share an instance of a class between two plugins. If you link that statically, it won't work at all.

Ok, so what could we do with NeL configurations ?

Add new dynamic configurations ?

I'm waiting to get a confirmation from NeL leads before to do something :)