The only other thing I can think of is that I don't run any of those commands as sudo to create the binary. If you mix/match priviledge/non-priviliedged execution, something will likely have a permission problem and fail. To generate the binary this is my bash history verbatim.<div>
<br></div><div><div> 540 mkdir build-mike</div><div> 541 cd source/</div><div> 542 git pull</div><div> 543 git submodule update</div><div> 544 cd ..</div><div> 545 cd build-mike/</div><div> 546* cmake -DBUILD_SHARED_LIBS:BOOL=ON -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_INSTALL_PREFIX=/Users/Shared/Toolkits/ParaView-3.10.1 -DCMAKE_OSX_ARCHITECTURES:STRING="x86_64" -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="10.5" -DCMAKE_OSX_SYSROOT:PATH="/Developer/SDKs/MacOSX10.5.sdk" ../source/</div>
<div><launched cmake-gui to set qmake location></div><div> 547 make -j18</div><div> 548 cpack -G DragNDrop --config Applications/ParaView/CPackParaViewConfig.cmake </div><div><br></div><br><div class="gmail_quote">
On Tue, May 24, 2011 at 8:31 AM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hmm. I am not seeing anything in there that is different from my setup<br>
besides the Qt version. I have tried both 4.6.3 and 4.7.2 of Qt and<br>
CMake versions 2.8.3 and 2.8.4. All with the same issue. Maybe asking<br>
on the Qt interest list if anyone has ever seen this type of behavior<br>
before?<br>
_________________________________________________________<br>
Mike Jackson <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
<div><div></div><div><br>
<br>
On Tue, May 24, 2011 at 8:14 AM, David Partyka<br>
<<a href="mailto:david.partyka@kitware.com" target="_blank">david.partyka@kitware.com</a>> wrote:<br>
> Qt 4.6.3 built by hand with cocoa, the binary is x64 only targeting 10.5. I<br>
> am building from the tip of the 'release' branch.<br>
> Qt Configure command:<br>
> export QMAKE_MACOSX_DEPLOYMENT_TARGET=10.5<br>
> ./configure<br>
> --prefix=/Users/partyd/Dashboards/Support/qt-4.6.3-MacOSX10.5/bin -nomake<br>
> demos -nomake examples -arch x86_64 -opensource -release -cocoa -shared<br>
><br>
> I also pass these in as -D arguments on initial configure with cmake.<br>
> set(CMAKE_OSX_ARCHITECTURES "x86_64" CACHE STRING "force build for 64-bit<br>
> Leopard" FORCE)<br>
> set(CMAKE_OSX_DEPLOYMENT_TARGET "10.5" CACHE STRING "force build for 64-bit<br>
> Leopard" FORCE)<br>
> set(CMAKE_OSX_SYSROOT "/Developer/SDKs/MacOSX10.5.sdk" CACHE PATH "force<br>
> build for 64-bit Leopard" FORCE)<br>
> On Mon, May 23, 2011 at 10:30 PM, Michael Jackson<br>
> <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>> wrote:<br>
>><br>
>> Dave,<br>
>> What is the configuration you are using? Qt Version? As Carbon or Cocoa?<br>
>> Universal Binaries or x64 only? Self build or download from Nokia?<br>
>><br>
>> What tag from paraview git repository are you using? I may be able to get<br>
>> my environment going like yours.<br>
>><br>
>> I also tried the latest ParaView master from head and my plugins need to<br>
>> be updated for that to work so using that is out of the question at this<br>
>> point.<br>
>><br>
>> This is what I have tried and have not worked:<br>
>> Qt 4.6.2 Self built with NO custom plugins<br>
>> Qt 4.7.2 Self built with NO custom plugins<br>
>> "make install" of both of the above.<br>
>> using sudo for everything to avoid possible permissions issues.<br>
>><br>
>> I'll download the prebuilt Qt libraries from Nokia and try those. I guess<br>
>> I could also try CMake 2.8.4<br>
>> ___________________________________________________________<br>
>> Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
>> Principal Software Engineer <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
>> BlueQuartz Software Dayton, Ohio<br>
>><br>
>><br>
>><br>
>> On May 23, 2011, at 6:33 PM, David Partyka wrote:<br>
>><br>
>> > Can you provide the initial cmake configuration details of your vanila<br>
>> > paraview build?<br>
>> ><br>
>> > On Mon, May 23, 2011 at 6:02 PM, Michael Jackson<br>
>> > <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>> wrote:<br>
>> > I tried this also:<br>
>> ><br>
>> > 562:[mjackson@ferb2:4.6.2]$ sudo rm -rf _CPack_Packages/; sudo cpack -G<br>
>> > ZIP --config Applications/ParaView/CPackParaViewConfig.cmake<br>
>> > CPack: Create package using ZIP<br>
>> > CPack: Install projects<br>
>> > CPack: - Run preinstall target for: ParaView Runtime Libs<br>
>> > CPack: - Install project: ParaView Runtime Libs<br>
>> > CPack: - Run preinstall target for: HDF5 Core Library<br>
>> > CPack: - Install project: HDF5 Core Library<br>
>> > CPack: - Run preinstall target for: VTK Runtime Libs<br>
>> > CPack: - Install project: VTK Runtime Libs<br>
>> > CPack: - Run preinstall target for: ParaView Components<br>
>> > CPack: - Install project: ParaView Components<br>
>> > CPack: Create package<br>
>> > CPack Error: Problem while adding file<<br>
>> > /Users/Shared/OpenSource/ParaView-<a href="tel:3.10.1%2F4.6.2" value="+13101462" target="_blank">3.10.1/4.6.2</a>/_CPack_Packages/Darwin-i386/ZIP/ParaView-3.10.1-Darwin-i386/lib/paraview-3.10/libCosmo.dylib><br>
>> > to archive<br>
>> > </Users/Shared/OpenSource/ParaView-<a href="tel:3.10.1%2F4.6.2" value="+13101462" target="_blank">3.10.1/4.6.2</a>/_CPack_Packages/Darwin-i386/ZIP/ParaView-3.10.1-Darwin-i386.zip><br>
>> > .ERROR =archive_write_header: Filetype not supported<br>
>> > CPack Error: Problem compressing the directory<br>
>> > CPack Error: Error when generating package: ParaView<br>
>> ><br>
>> ><br>
>> > And that was built against Qt 4.6.2.<br>
>> > ___________________________________________________________<br>
>> > Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
>> > Principal Software Engineer <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
>> > BlueQuartz Software Dayton, Ohio<br>
>> ><br>
>> > On May 23, 2011, at 5:56 PM, David Partyka wrote:<br>
>> ><br>
>> > > I am really unsure, I haven't ever seen these kinds of errors before<br>
>> > > and I am unable to reproduce this. sla.r on my system appears to just<br>
>> > > contain license information. Have you tried manually removeing the<br>
>> > > _CPack_Packages directory in your build tree to see if for some reason cpack<br>
>> > > isn't able to blow it away entirely?<br>
>> > ><br>
>> > > On Mon, May 23, 2011 at 5:24 PM, Michael Jackson<br>
>> > > <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>> wrote:<br>
>> > > When running CPack on a "clean" paraview build directory where NONE of<br>
>> > > my plugins are being build I get the following after trying to run CPack:<br>
>> > ><br>
>> > > cpack -G DragNDrop --config<br>
>> > > Applications/ParaView/CPackParaViewConfig.cmake<br>
>> > > .....<br>
>> > ><br>
>> > ><br>
>> > > /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/sla.r:522:<br>
>> > > ### /usr/bin/Rez - String spans lines.<br>
>> > ><br>
>> > > /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/sla.r:<br>
>> > > ### /usr/bin/Rez - Since errors occurred,<br>
>> > > /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/temp-udco.dmg's<br>
>> > > resource fork was not completely updated.<br>
>> > ><br>
>> > > /Users/Shared/OpenSource/ParaView-3.10.1/Build/_CPack_Packages/Darwin-i386/DragNDrop/sla.r:<br>
>> > > ### /usr/bin/Rez - SysError -37 during set file info.<br>
>> > ><br>
>> > > CPack Error: Problem compressing the directory<br>
>> > > CPack Error: Error when generating package: ParaView<br>
>> > ><br>
>> > ><br>
>> > ><br>
>> > > ___________________________________________________________<br>
>> > > Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
>> > > Principal Software Engineer <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
>> > > BlueQuartz Software Dayton, Ohio<br>
>> > ><br>
>> > > On May 23, 2011, at 4:32 PM, David Partyka wrote:<br>
>> > ><br>
>> > > > I've never seen anything like that, as that is the same process I<br>
>> > > > used to make the 3.10.1 binaries. Though I did use cmake 2.8.4. Are you<br>
>> > > > using a really new Qt or something along those lines?<br>
>> > > ><br>
>> > > > On Mon, May 23, 2011 at 4:19 PM, Michael Jackson<br>
>> > > > <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>> wrote:<br>
>> > > > I followed the directions on the wiki page to compile my own<br>
>> > > > ParaView 3.10.1 because I have some custom plugins that I compile. The .dmg<br>
>> > > > image was created just fine but the contained "ParaView.app" when launched<br>
>> > > > only has a menu bar that has "New Application" menu. Nothing else. Yet when<br>
>> > > > I run it from the Build folder everything works just fine. Is there<br>
>> > > > something in the cmake configuration of ParaView that I need to set that<br>
>> > > > tells CMake that I am going to making a redistributable package? The same<br>
>> > > > thing happens if I try a "make install" from the command line. This is on OS<br>
>> > > > X 10.6.8 with CMake 2.8.3 and the ParaView 3.10.1 sources from the web site.<br>
>> > > > ___________________________________________________________<br>
>> > > > Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
>> > > > Principal Software Engineer <a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a><br>
>> > > > BlueQuartz Software Dayton, Ohio<br>
>> > > ><br>
>> > > > _______________________________________________<br>
>> > > > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> > > ><br>
>> > > > Visit other Kitware open-source projects at<br>
>> > > > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> > > ><br>
>> > > > Please keep messages on-topic and check the ParaView Wiki at:<br>
>> > > > <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>> > > ><br>
>> > > > Follow this link to subscribe/unsubscribe:<br>
>> > > > <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>> > > ><br>
>> > ><br>
>> > ><br>
>> ><br>
>> ><br>
>><br>
><br>
><br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
</div></div></blockquote></div><br></div>