#4 support for runtime library linking

[fantaz]

Hi,
Under wxWidgets build properties dialog, it would be very nice if under main build options one can select runtime library linking (/MTd etc. compiler flags). I heavily use static linking, while wxwidgets by default uses dynamic. Maybe the autodetect feature will recognize these options?
Is a valid Package repository URL set?
For this one (http://mathdev.sourceforge.net/wxp/samples.wxl) the wxWidgets Package Manager puts out error
"Invalid remote repository.... "

[Francesco Montorsi]

Logged In: YES
user_id=591038
Originator: NO

Hi,
about static library linking: I can add support for it but as for all other options which define the wxWidgets build, the problem is that the package's build systems must be able to support it as build option.

To explain better: when from the wx build dialog you tell wxPM that you have a Unicode build of wx, it only stores this setting and then later when building a package which exposes an option named "WX_UNICODE", it will automatically set it to the "1" before building the package.

Now, this is only a matter of "standard option names": i.e. the WX_* option values remembered by wxPM are currently those associated with the wxpresets bakefiles: WX_UNICODE/VERSION/DEBUG/DIR/etc.

However there's no standard bakefile presets option name for the static linking, so, all in all, I'd say it's a matter of the packager to put in the .wxp file of its package the lines which say to wxPM: "hey, when showing the user the build options for this package, also show the RUNTIME_LIBS=static/dynamic option as my package's build system supports it".

[Francesco Montorsi]

Logged In: YES
user_id=591038
Originator: NO

About the valid package repository URL (please submit things as separed tracker items): the default repository url should be http://wxwpm.sourceforge.net/packages

If you see that old repo URL it's probably because of a residual of previous versions: using regedit delete the Software -> wxPackageManagementSuite folder from your registry and rerun wxPM - this should fix it.

[fantaz]

Logged In: YES
user_id=952458
Originator: YES

About static lib linking: I saw that feature on dialogblocks, and i agree with you. However, I wouldn't leave these options to the packager. It's just that someone would use it and someone wouldn't. It should be up the the user how he want's this package to be built. If he has static(lib) linking, than tha package should be statically linked. Otherwise, there are linking errors on vs2005. And to find what's wrong on someone's elses code, or build can be pain in the... It's just that build options should be there and let the user choose how the package should be built(linked to be precise). Anyway, I could be wrong, but i do speek from my experience. I had changed these setting dozens of times for other libs and/or other wx programs, but when setting the project options with dialogblocks, one only has to select the option.
best regards,
fantaz