Re: proposed change in profile-relative file locations

[Conrad Carlen]

Simon Fraser wrote:

[EMAIL PROTECTED]">

Conrad Carlen wrote:

1. Use the profile mgr
2. Use a litle lib in modules/mpfilelocprovider - gtkWidget does this,
possibly other embedding apps

        What I'd like to do is get rid of modules/mpfilelocprovider, still build
a static lib, but build it in the profile module. The profile dll would
link with it, but the static lib would be exported so an embedding app
could link with it.

The embedding app may not be a C/C++ application. So it won't always
be able to link with a static lib.

Anything that links with the current mpfilelocprovider static lib or EmbedAPI static lib could. What sort of app were you thinking of?

[EMAIL PROTECTED]">

Or do I misunderstand you?

All I'm talking about is moving/re-factoring some existing code and requiring that file locations (one method or the other) are always available. The requirement part is why I brought it up here.

[EMAIL PROTECTED]">

Simon