The bitness comes from ParaViewCommon.cmake around line 280 and passed into build_paraview_client in Applications/ParaView/CMakeLists.txt around line 49. I guess in this case the title should be Universal, what do you think? I have similar logic that generates the dmg name that way. i.e. if there are more than one target platforms then call it Darwub-Universal.<div>
<br></div><div><br><div class="gmail_quote">On Mon, Feb 7, 2011 at 11:00 AM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net">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;">
Yes. I was doing a universal build targeted for 10.5 but using a 10.6 to build. Do you have a hint as to where that title is generated? I'll try and put together a patch.<br>
<div class="im"><br>
___________________________________________________________<br>
Mike Jackson <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
<br>
<br>
</div><div><div></div><div class="h5">On Feb 7, 2011, at 10:57 AM, David Partyka wrote:<br>
<br>
> Humm, curious if you doing a universal build then? Yeah please file a bug and I'll make sure it's fixed for 3.10.0 final.<br>
><br>
> On Mon, Feb 7, 2011 at 10:37 AM, Michael Jackson <<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>> wrote:<br>
> Just compiled the latest ParaView from git (master) and when I launched the app I noticed at the top that it had "32 Bit" in the title. Just to verify my version was actually a 64 bit version. My guess is that when that title is generated in code there should be some preprocessor logic to figure out just how it was built. Relying on the sizeof(void*) probably isn't the best idea:<br>
><br>
><br>
> #if !defined(__APPLE__)<br>
> Compute title for NON Apple Platforms<br>
> #else<br>
> # if defined(__LP64__) && __LP64__<br>
> 64 BIt title<br>
> # else<br>
> 32 bit title<br>
> # endif<br>
><br>
> #endif<br>
><br>
> Should I put in a formal bug report?<br>
><br>
> Thanks<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">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 <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>
><br>
<br>
</div></div></blockquote></div><br></div>