Alan W. Irwin wrote:
> On 2010-01-08 20:23-0500 Hazen Babcock wrote:
>
>> On windows we should probably check the version of Python and adjust the
>> name accordingly.
>
> The implication of some mailing list results I googled for after seeing your
> above post, is that Windows Python has support
On 2010-01-08 20:23-0500 Hazen Babcock wrote:
> So I was able to get Plplot & Python to work [on Windows] by changing
> "_plplotcmodule.dll" to "_plplotc.pyd" (note "_plplotcmodule.pyd" does
> not work) and making sure the all the PLplot dll's are in my system path.
Glad you discovered that.
>
>
Hazen Babcock wrote:
> Werner Smekal wrote:
>> On Jul 15, 2009, at 7:14 PM, Hazen Babcock wrote:
>>> (2) When I try to run a python example I get "ImportError: No module
>>> named _plplotc". I have python2.6, numpy 1.3.0 and swig(swigwin?)
>>> 1.3.39. Is there anything special that I need to do to
On 2009-07-23 21:34, Hazen Babcock wrote:
> Alan W. Irwin wrote:
>> Hi Hazen:
>>
>> This is mostly addressed to you, but there is a question at the end for all
>> our developers.
>>
>>
>> I am inclined to simply say in the release notes that until CMake bug 9220
>> is fixed, we do not support any m
Werner Smekal wrote:
> On Jul 15, 2009, at 7:14 PM, Hazen Babcock wrote:
>> (2) When I try to run a python example I get "ImportError: No module
>> named _plplotc". I have python2.6, numpy 1.3.0 and swig(swigwin?)
>> 1.3.39. Is there anything special that I need to do to use Python/
>> PLplot
>> o
Alan W. Irwin wrote:
> Hi Hazen:
>
> This is mostly addressed to you, but there is a question at the end for all
> our developers.
>
> On 2009-07-23 12:23-0400 Hazen Babcock wrote:
>
>> [...]I think I managed to figure out a few things. Maybe the problem
>> is with the cmake command that is use
Hi Hazen:
This is mostly addressed to you, but there is a question at the end for all
our developers.
On 2009-07-23 12:23-0400 Hazen Babcock wrote:
> [...]I think I managed to figure out a
> few things. Maybe the problem is with the cmake command that is used to test
> the c++ compiler (the on
Alan W. Irwin wrote:
> On 2009-07-22 22:51-0400 Hazen Babcock wrote:
>
>> Alan W. Irwin wrote:
>>> I believe I have now (revision 10157) finished this saga. The new
>>> soft-landing method (issue a warning message, disable that component of
>>> PLplot, and continue) when compilers are missing/bro
On 2009-07-22 22:51-0400 Hazen Babcock wrote:
> Alan W. Irwin wrote:
>> I believe I have now (revision 10157) finished this saga. The new
>> soft-landing method (issue a warning message, disable that component of
>> PLplot, and continue) when compilers are missing/broken seems to work well.
> [..
Alan W. Irwin wrote:
> On 2009-07-16 14:04-0700 Alan W. Irwin wrote:
>
>>> On 2009-07-15 22:46-0700 Alan W. Irwin wrote:
>>>
[...]To summarize the choice we can have
no soft landings or no cmake-gui.
>> I have just committed (revision 10153) the hard-landing solution because
>> there is
On 2009-07-16 14:04-0700 Alan W. Irwin wrote:
>> On 2009-07-15 22:46-0700 Alan W. Irwin wrote:
>>
>>> [...]To summarize the choice we can have
>>> no soft landings or no cmake-gui.
>
> I have just committed (revision 10153) the hard-landing solution because
> there is no way I wanted to have both
Hi,
I believe cmake can be told to be very verbose about its configuring.
Don't have time now, but a quick search showed that
cmake --debug-output
might be of any help to you.
Regards,
Werner
On Jul 17, 2009, at 4:48 PM, Hazen Babcock wrote:
> Hazen Babcock wrote:
>> Alan W. Irwin wrote:
>>
Hazen Babcock wrote:
> Alan W. Irwin wrote:
>> On 2009-07-15 17:53-0400 Hazen Babcock wrote:
>>
>>> Alan W. Irwin wrote:
[...]Furthermore, if you are still getting a warning (now) about a missing
C++
compiler, I frankly don't understand why 5.9.4 works for you at all without
er
> On 2009-07-15 22:46-0700 Alan W. Irwin wrote:
>
>> [...]To summarize the choice we can have
>> no soft landings or no cmake-gui.
I have just committed (revision 10153) the hard-landing solution because
there is no way I wanted to have both ccmake and cmake-gui provide broken
language results suc
Alan W. Irwin wrote:
> On 2009-07-15 17:53-0400 Hazen Babcock wrote:
>
>> Alan W. Irwin wrote:
>>> [...]Furthermore, if you are still getting a warning (now) about a missing
>>> C++
>>> compiler, I frankly don't understand why 5.9.4 works for you at all without
>>> erroring out at cmake time. The
Hazen Babcock wrote:
> Werner Smekal wrote:
>> I don't believe that the gdi32 library is your problem. Look at the
>> code in wingcc.cmake:
>>
>>message(STATUS "Looking for gdi32 header and library")
>>find_library(GDI32_LIBRARY gdi32 HINTS ${MINGWLIBPATH} $
>> {BORLANDLIBPATH})
>>if
Werner Smekal wrote:
>
> I don't believe that the gdi32 library is your problem. Look at the
> code in wingcc.cmake:
>
>message(STATUS "Looking for gdi32 header and library")
>find_library(GDI32_LIBRARY gdi32 HINTS ${MINGWLIBPATH} $
> {BORLANDLIBPATH})
>if(GDI32_LIBRARY)
> fin
On 2009-07-15 22:46-0700 Alan W. Irwin wrote:
> [...]To summarize the choice we can have
> no soft landings or no cmake-gui.
>
> Which is the preferred choice that we use until this can of worms is cleaned
> up by the CMake developers?
>
> I would be happy to implement whatever we decide and write
Hi Hazen,
>>
>
> I believe everything is the same. I am using the CMake GUI
> configuration
> utility and not the command line cmake (due to the apparent gdi32
> issue). The problem is that cmake-gui-plplot-5.9.4 considers my C++
> compiler to be findable/acceptable whereas cmake-gui-plplot-svn d
On 2009-07-15 16:19-0700 Alan W. Irwin wrote:
> If under those conditions cmake works, but the cmake GUI does not for the
> svn trunk version, then that probably means my recent changes in how C++ is
> found have exposed a bug in cmake-gui.
I confirm this cmake-gui issue on Linux with the PLplot
On 2009-07-15 17:53-0400 Hazen Babcock wrote:
> Alan W. Irwin wrote:
>> [...]Furthermore, if you are still getting a warning (now) about a missing
>> C++
>> compiler, I frankly don't understand why 5.9.4 works for you at all without
>> erroring out at cmake time. The C++ language was an absolute
Alan W. Irwin wrote:
> On 2009-07-15 19:29+0100 Andrew Ross wrote:
>
>> On Wed, Jul 15, 2009 at 01:14:59PM -0400, Hazen Babcock wrote:
>>> (1) Do we have a minimum c++ version requirement? I couldn't find
>>> anything in the archives but when I tried to run cmake on svn head I get
>>> this error:
On 2009-07-15 19:29+0100 Andrew Ross wrote:
> On Wed, Jul 15, 2009 at 01:14:59PM -0400, Hazen Babcock wrote:
>>
>> (1) Do we have a minimum c++ version requirement? I couldn't find
>> anything in the archives but when I tried to run cmake on svn head I get
>> this error:
>>
>> CMake version = 2.6.
Werner Smekal wrote:
> Hi Hazen,
>
> On Jul 15, 2009, at 7:14 PM, Hazen Babcock wrote:
>
>> (1) Do we have a minimum c++ version requirement? I couldn't find
>> anything in the archives but when I tried to run cmake on svn head I
>> get
>> this error:
>>
>> CMake version = 2.6.4
>> The CXX comp
On Wed, Jul 15, 2009 at 01:14:59PM -0400, Hazen Babcock wrote:
>
> (1) Do we have a minimum c++ version requirement? I couldn't find
> anything in the archives but when I tried to run cmake on svn head I get
> this error:
>
> CMake version = 2.6.4
> The CXX compiler identification is GNU
> CMak
Hi Hazen,
On Jul 15, 2009, at 7:14 PM, Hazen Babcock wrote:
>
> (1) Do we have a minimum c++ version requirement? I couldn't find
> anything in the archives but when I tried to run cmake on svn head I
> get
> this error:
>
> CMake version = 2.6.4
> The CXX compiler identification is GNU
> CMake
(1) Do we have a minimum c++ version requirement? I couldn't find
anything in the archives but when I tried to run cmake on svn head I get
this error:
CMake version = 2.6.4
The CXX compiler identification is GNU
CMake Error at cmake/modules/c++.cmake:57 (message):
C++ compiler absolutely req
27 matches
Mail list logo
