Hello Johannes,

On 02/18/2013 03:34 AM, Johannes Brunen wrote:
> I would like to propose that we do the following:
>
> 1. Explicitly partitioning of the options into categories, for example:
>
>                  a) What is being build: Test, Examples, Python,
> Documentation...
>
>                  b)  How it is build, i.e. ABI related stuff, sse2,..
>
>                  c) Packaging support
>
>                  d) Debugging support
>
>                  e) Platform: e.g. OSG_ENABLE_OGL_COREONLY
>
>                  f) Features: e.g. OSG_ENABLE_NEW_OSB_IO
>
>                  g) Experimental, Temporary: e.g.
> OSG_ENABLE_MULTISHADER_VARCHUNK
>
>                  h) Environment: e.g. OSG_ENABLE_GL_INCLUDE_GLEW
>
>                  i) Internal: e.g. OSG_ENABLE_FCD2CODE

looks like a good starting point to me. I'd suggest trying to keep the 
number of categories as small as possible, that would make it simpler to 
place new options in the correct category. Along those lines: perhaps 
merge Experimental in Internal into just Internal?

> 2. Document the categories
>
> 3. Document the options: Its purpose and relevance as well as its
> overall effect.
>
> 4. Provide value ranges for non boolean options: e.g.
> OSG_SHADER_CACHE_MODE

IIRC this particular one exists/existed to allow Gerrit to do 
performance testing and should now default to what he determined to be 
the optimal setting ;)
That is of course specific to this variable, in general I agree with 
your plan :)

> To be clear, this is not a critique on the build system at all. I only
> wish to clarify and simplify the optional build space of OpenSG.
>
> What do you think?
>
> Do you like the idea of in place documentation in the CMakeLists.txt
> file?

yes, that way it is where the variables/options are defined, so has a 
higher chance of being updated.

        Cheers,
                Carsten

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to