Re: Compiling OpenShadingLanguage under Windows
I have been trying to get the shaders test to build but I have run into lots of issues with linking dependencies, exports imports etc.toggle quoted message Show quoted text
The projects cmake generates for example oslquery uses source files from olsexec. This is causing issues with the DLL_PUBLIC etc type of declerations, because other projects use oslexec as a library to import.
I guess this may work fine on GCC but windows is pitches a fit, because in one project the defines are correct import/export in the other they are import when they should be nothing or export.
Are the source files being duplicated in the projects on purpose? Is this just a cmake issue?
Is this just an issue with VS because GCC doesn;t care and just links everything together?
I think i should be able to rearrange the import/export types for windows, and then make olsquery have a depencency to oslexec instead of rebuilding the lexer etc. And for any of the other projects(i think the others are better).
And make sure the projects use the library imports rather than building the code themselves?
Or should i get them to build duplicating the code in areas and just fix the special cases with more defines.
I prefer the first option, and at first i could probably isolate it to windows in cmake and the source. But maybe its a issue for gcc as well in some areas.
Or maybe oslquery needs to run standalone you dont want to inlcude a dll/so.
On Thu, Jan 21, 2010 at 12:39 AM, Wormszer <worm...@...> wrote: