If you want the constructor exported, you should export the class (which
exports all of its public API), not a single function within the class.
Also, if you export a class, all of its parent classes should also be
exported.
On Tue, Jul 6, 2010 at 7:56 AM, Fred Fred wrote:
> Because I tried i
Yes, it is intended, and has to do with the dual nature of the ParaView Mac
installation. (It's a bundle app, it's a unix command line tool, you
decide...)
Use:DESTDIR=blah make install
and it will end up in "$blah/Applications" instead of "/Applications"
If we put it where CMAKE_INSTALL_PREFIX
And, BTW, if you don't have write privileges to "/Applications" then you
should get some sort of error message when doing the "make install" -- let
us know if that's not the case.
On Wed, Aug 5, 2009 at 4:47 PM, David Cole wrote:
> Yes, it is intended, and has
=/Users/Shared/Toolkits/ParaView-3.6-x64
> "
> )
> ctest_configure (BUILD "${CTEST_BINARY_DIRECTORY}")
> ctest_read_custom_files(${CTEST_BINARY_DIRECTORY})
> ctest_build (BUILD "${CTEST_BINARY_DIRECTORY}")
> ctest_test (BUILD "${CTEST_BINARY_DIRECTORY}" EXCLUDE
> "Global
In a new style script, get rid of the MAKECOMMAND from the cache and do this
in the ctest -S script:
set(CTEST_BUILD_FLAGS -j16)
HTH,
David
On Thu, Jun 11, 2009 at 3:30 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> After following lots of advice from another thread I am finally
You can't make your build show up in ParaView 3.6 -- only the "project
admin" for ParaView can do that on the CDash server. So... after you are all
set, just let us know what the "site name" and "build name" are for your 3.6
submission and we'll get the project admin to categorize your build...
You
In an old style script like the one Utkarsh pointed to, include a definition
for "CVS_UPDATE_OPTIONS:STRING=-d -A -P -r ParaView-3-6" in the
CTEST_INITIAL_CACHE variable. (The important parts being the -r branch-name
args...)
In a new style script that uses ctest_update() and ctest_build() and so
You have to use "-d" with your cvs updates to get new directories
I always use:
cvs up -dAP
to sync my dev trees to CVS HEAD.
On Fri, Apr 24, 2009 at 11:27 AM, John Drescher wrote:
> On Fri, Apr 24, 2009 at 11:16 AM, Timothy M. Shead
> wrote:
> > John Drescher wrote:
> >>
> >> I updated my
currently in flux in CVS HEAD of VTK, or
needs some work, or shouldn't be in a release, or anything like that.
please do reply to this email and let us know.
Thanks,
David Cole
Kitware, Inc.
2009/1/19 Bob Obara
> In the next couple weeks we are planning to start the process of
I'm assuming you are building a 32-bit binary (because there is no 64-bit
Carbon to link to)
Sean, would you mind (1) fixing this or (2) reverting your
vtkCarbonRenderWindow change of 1.75 until somebody can figure out what it
takes to fix this...?
I think we should view vtkCarbonRenderWindow
In the meantime, would you revert your change so we can otherwise approach
green on the VTK dashboard?
It seemed to be largely getting closer to green for about two weeks up till
that change and it would be nice to see the progress instead of having
TemporalFractal test failing everywhere it runs f
Also merged to the VTK-5-2 branch:
/cvsroot/VTK/VTK/Rendering/vtkOpenGLExtensionManager.cxx,v <--
Rendering/vtkOpenGLExtensionManager.cxx
new revision: 1.31.2.1; previous revision: 1.31
On Tue, Nov 25, 2008 at 2:44 PM, Berk Geveci <[EMAIL PROTECTED]>wrote:
> Hi Gerard,
>
> This is now
If you want to debug things with the Microsoft compiler on Windows, you have
to build *everything* loaded into the process as a "Debug" configuration. It
is worth the extra time taken to do this. Otherwise, you will simply have
mysteries on your hands and you will spend countless hours pulling your
You need to do a "make install" to produce the standalone bundle.
I recommend using...:
DESTDIR=pvinst make install
...and then getting the standalone bundle out of the pvinst directory...
Why do you say the build directory is needed to launch it? What happens if
you move/rename the build directo
and
resolve it...
Thanks,
David Cole
P.S. -- Nobody likes a scrooge-y Dave Cole this time of year. Help keep the
holiday seasons filled with good cheer. ;-)
___
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview
Line 506 says: FILE(GLOB QT_LIB_LIST RELATIVE ${QT_LIB_DIR_tmp}
"${QT_${qtlib}_LIBRARY_RELEASE}*")
What is QT_LIB_DIR_tmp on your machine?
MESSAGE(STATUS "QT_LIB_DIR_tmp='${QT_LIB_DIR_tmp}'")
I'm betting it's empty based on your problem. (And not for anybody else...)
So: why is it empty for
This issue...http://public.kitware.com/Bug/view.php?id=6363
...covers CPack created packages for Win64 defaulting to the wrong "Program
Files" directory. After that bug is fixed, and the next ParaView Win64
installer is built with a fixed version of CPack, ParaView's installer
should automatically
I have found things the easiest with a google search with "site:paraview.org"
appended to the end...
HTH,
David
On Fri, Sep 12, 2008 at 2:11 PM, Pei-Ying Hsieh <[EMAIL PROTECTED]>wrote:
> Dear Paraview group:
>
> How to search the paraview email archive?
>
> Thanks!
>
> Pei
>
>
> __
ere when you
> allocate an array of size 0, it actual creates a buffer rather than just
> returning NULL.
> >
> > I just checked in a change that does not call new if nameLength is 0.
> Let me know if there are still problems.
> >
> > -Ken
> >
> >
> > From: David
19 matches
Mail list logo
