On 2011-04-11 22:40, Nicky Perian wrote:
Quicktime SDK is an INSTALL_PROPRIETARY=TRUE archive download. The LL
archive is modified to work with VS2010. The Apple Quicktime SDK has
not been modified and fails compile.
Can you expand on that last statement?
I cloned 3p-quicktime and with autobuild build and package have the
libraries. The procedure worked extremely well.
Yay!
Then, I modified autobuild.xml to point to the local copy. Now the
catch, since QuickTimePlugin.cmake has:
if (INSTALL_PROPRIETARY)
include(Prebuilt)
use_prebuilt_binary(quicktime)
endif(INSTALL_PROPRIETARY)
What autobuild setup or command line switch do I use to access the
local copy?
I commented out the if(INSTALL_PROPRIETARY) and then it pulled from
the local copy with autobuild.xml set to the location and md5sum
printed as output of autobuild package command.
What are the planned methods to use local copies of what at one time
were proprietary or license restricted packages and now can be cloned
and built on a local computer and used?
Also, does INSTALL_PROPRIETARY make sense when the end result is the
library is on the local computer and can be used?
This is a good general issue.
My feeling is that we should add a switch for each of these optional
packages. The per-package switch (in this case, perhaps
INSTALL_PKG_QUICKTIME) would replace INSTALL_PROPRIETARY everywhere it
is used to make a package-specific decision now, and in one of the
common cmake files we add a block that provides default values for all
the INSTALL_PKG_* switches based on INSTALL_PROPRIETARY.
We don't need to do this for every package - it's not worth the trouble
to do it for things that everyone has access to, but having a pattern to
use for the ones that have some distribution limitations seems useful.
Sound workable?
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
