On 11/07/2014 01:00 PM, Alan W. Irwin wrote: > Hi Hazen: > > Arguing by analogy with the similar pkg-config case, I don't think > removing INCLUDEPATH is the correct thing to do in plplotqt.pro (where > that file is used by qmake to generated compile and link flags for > users similarly to the way that pkg-config does the same thing from > information collected in *.pc files). So I have handled INCLUDEPATH a > different way in plplotqt.pro(.in). For further discussion see the > commit message for 03ad89d. This is my first experience with *.pro > files so if my analysis of their documentation is incorrect, feel free > to make further changes. But regardless of that, please follow up on > the ToDo item at the end of the commit message (i.e., figure out where > the best place would be to install plplotqt.pro in the install tree, > and then implement that installation).
I'm pretty sure that we don't need plplotqt.pro at all. I thought it was used during the plplot build process by qmake in order to compile libsmokeplplotqt, however as you point out that is not what it's for. Since it exists solely for that purpose I don't think it has any utility. Other projects that might use our smoke bindings don't need to know how to compile this library since it should already be compiled. -Hazen ------------------------------------------------------------------------------ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
