In the 3.5.13.x branch, dbus-tqt and dbus-1-tqt were required to install to /usr rather than $PREFIX (usually /opt/trinity).
In the R14 branch that was changed. At least, I have been
building
both to install to /opt/trinity since I started building R14 in the early days of the branch.
Are/should those packages be built to install to /usr?
Is tqtinterface still required to be built to install to /usr?
Are any other packages required to built to install to /usr?
Anybody? This affects all developers.
Sorry, this doesn't affect me any more as I haven't done anything with the 3.5.13 branch for ages now. I'd help if I could only remember... ;-)
I did not phrase my question correctly. Is R14 affected by those install requirements? Or can all modules be installed to /opt/trinity?
Darrell
In the 3.5.13.x branch, dbus-tqt and dbus-1-tqt were required to install to /usr rather than $PREFIX (usually /opt/trinity).
In the R14 branch that was changed. At least, I have been
building
both to install to /opt/trinity since I started building R14 in the early days of the branch.
Are/should those packages be built to install to /usr?
Is tqtinterface still required to be built to install to /usr?
Are any other packages required to built to install to /usr?
Anybody? This affects all developers.
Sorry, this doesn't affect me any more as I haven't done anything with the 3.5.13 branch for ages now. I'd help if I could only remember... ;-)
I did not phrase my question correctly. Is R14 affected by those install requirements? Or can all modules be installed to /opt/trinity?
Darrell
Ah, I get it now. ;-)
AFAIK tqt3 still needs to be installed to /usr, not sure about tqtinterface as there has been a lot of CMake/Automake work for R14. The two TQt/DBUS binding libraries *should* be able to work from /opt/trinity, if they don't, then it's is probably a bug.
-
Darrell Anderson -
Timothy Pearson