On Mon, Aug 3, 2009 at 4:50 PM, Alan W. Irwin wrote:
> On 2009-08-02 23:21-0700 Alan W. Irwin wrote:
>
>> [...]I just realized
>> a similar fix (create moc_files.h which #includes the moc-generated
>> source)
>> is required for the static drivers case, but instead of going through this
>> in a 3rd
On 2009-08-02 23:21-0700 Alan W. Irwin wrote:
> [...]I just realized
> a similar fix (create moc_files.h which #includes the moc-generated source)
> is required for the static drivers case, but instead of going through this
> in a 3rd location in our build system, I am going to run moc and create
On 2009-08-02 21:44-0700 Alan W. Irwin wrote:
> Some time tomorrow I hope that we will be able to build the qt device driver
> with -DENABLE_qt=OFF, but that doesn't work at the moment[...]
Should work now (revision 10203), but this is just a temporary
implementation that I plan to generalize tom
On 2009-08-03 00:13-0400 Hezekiah M. Carty wrote:
> On Sun, Aug 2, 2009 at 10:29 PM, Alan W. Irwin
> wrote:
>> On 2009-08-01 22:37-0700 Alan W. Irwin wrote:
>>
>>> Hi Hez:
>>>
>>> The prior situation was that the C++ compiler was _always_ searched for
>>> (regardless of option settings) and if no
On 2009-08-01 22:37-0700 Alan W. Irwin wrote:
> Hi Hez:
>
> The prior situation was that the C++ compiler was _always_ searched for
> (regardless of option settings) and if not found an error resulted. Now it
> is optional depending on how ENABLE_cxx is set (with a soft landing if a C++
> compile
On 2009-08-01 18:05-0400 Hezekiah M. Carty wrote:
> I noticed today that disabling the C++ PLplot bindings now also
> disables the Qt output drivers. I do not think this was the case
> previously though I may be mistaken. I have not run cmake from a
> clean build directory in a while, so I am no
I noticed today that disabling the C++ PLplot bindings now also
disables the Qt output drivers. I do not think this was the case
previously though I may be mistaken. I have not run cmake from a
clean build directory in a while, so I am not sure when this changed.
Does the new compiler detection l
