project type change between static lib and others

[frankie]

Pelle,
this has been requested other times, but it really would be usefull to have possibility to change a project (or clone or the like) from a static lib to a DLL without redefining all sources, predefined symbols, etc.
While to switch from exe to DLL (and from a windows to console, and the reverse) is simply enough, it very difficult to change from a static library, because you can't change from polib to polink.
Thanks

P.S. About external files feature please take a look on the not working exclude and remove of sources.

[Pelle]

this has been requested other times, but it really would be usefull to have possibility to change a project (or clone or the like) from a static lib to a DLL without redefining all sources, predefined symbols, etc.
While to switch from exe to DLL (and from a windows to console, and the reverse) is simply enough, it very difficult to change from a static library, because you can't change from polib to polink.

Maybe in some future version; the change is too big for v8.0.

P.S. About external files feature please take a look on the not working exclude and remove of sources.

As I said many times before, the general idea is that source files for a project should be located in the project directory itself, or in a subdirectory below it. Picking and choosing source files from all over the disk isn't good practice, and should be banned. Making it too easy to work with "external" files isn't the way to go.

Maybe in the future add a way to copy "external" source files into the project directory, but again too much work for v8.0.

[frankie]

Thanks Pelle.
I understood and will wait for it 
You know the problem is not on new projects, that can be write following the PellesC rules, but the existing sw's out there. Their file structures are different, and normally doesn't provide bulding files for PellesC.
The use of precompiled libraries many times creates problems, rebuild the libraries is not so easy due to restrictions of PellesC projects rules.
The use of MS project import wizard copies the files in the development folder, but common files, on complex projects, become duplicated. Moreover this way you can't create a reusable building environment: i.e. when a new library version comes out everything have to be create as new ... 
This could be a severe limitation on use, there is a bunch of sw out there that can't be easily used....