Why are the 2.6.0 DLLs named "_vc_custom"?

[R]

I'm trying to build the 2.6.0 DLLs using VS.NET 2003 on WinXP.

The resulting libraries are named like:
wxbase26_vc_custom.dll
wxmsw26_adv_vc_custom.dll
...

.exp and .lib files don't have that strange postfix in their name (wxbase26.exp, wxbase26..lib, ...)

Is it safe to simply rename the libraries to
wxbase26.dll
wxmsw26_adv.dll
...

What's the reason for that strange naming?

*edit*
Just saw that the naming is explicitly set in the vcproj-files shipping with wxWidgets 2.6.0 - so this definitely is by design. On the other hand I can't find any documentation on why this is done and wether there is any official location to download these DLLs instead of building them by yourself - at least the name suggests that there is some official DLLs somewhere (that are not "custom")

[ABX]

[quote="R

[R]

Ok, I understand that. Thanks for the clarification. Although I'm not sure about the different compilers. How is that supposed to work, when there will be official DLLs, what compiler are the lib-files for?

There was intention to distribute "official" dlls and those are supposed to be not custom.

So, when will they be released? I thought 2.6.0 is already the current stable release...

[ABX]

[quote="R

[tiwag]

i've never heard about released libraries or dll's,
i always thought, wxwidgets is released as source distribution exlusively?

[Avi]

i've never heard about released libraries or dll's,
i always thought, wxwidgets is released as source distribution exlusively?

Well, that's not exact... They release RPMs for Linux... Look at wxGTK 2.4.2- there are many binary packages for it... 2.6.1's packages are not ready/released yet...

I think releasing some official DLL files would be a smart idea, but I wonder which build options would the official DLL use?

[tiwag]

They release RPMs for Linux... Look at wxGTK 2.4.2- there are many binary packages for it...

ahh yes, i see

I think releasing some official DLL files would be a smart idea, but I wonder which build options would the official DLL use?

that's really a dilemma,
anyway it's easier to build it for yourself.

[lroathe]

OK,

So I finally find this post to understand why I am not getting anything to build; within the project dependencies fail because they do not have "_vc_custom" in the library name but that is all that the VC project will build.

So, how does one get the "official" dll & lib files for Windows? Having looked I could not find any such download; so if it's not available how does one build the entire project (all targets, samples and demos) in VC since the projects in the 2.6.1 install do not work.

Thanks!

[lowjoel]

erm this MIGHT be unwanted, maybe a senior mod like ryan might wanna delete this... but if it has not been discussed, erm (im in a slow frame of mind) you can configure what appears in place of "custom" in the dll by editing config.vc (or .gcc or .bcc or whatever your compiler is) its near the bottom... i quote:

Code: Select all

# Use this to name your customized DLLs differently 
VENDOR = build

in my case ive called it build so it's now wxmsw26u_vc_build.dll im afraid if you want to edit the front parts you'll have to edit the makefile

[lroathe]

So I'm guessing that the real answer is not to use VC++ via the projects since changing that will not change the project files where the names are defined? (ie, don't use the .dsw/.dsp projects, use the makefile system intead?)

How does one go about doing that, esp. in the debugging department? (Windows is not my native environment, so I'm only familiar with VisualStudio style development at this point).

Thanks