[Ves] Errors during VES building using make -j4

[Aashish Chaudhary]

On Fri, Aug 30, 2013 at 10:35 AM, Xiaopeng Yang <yxp233 at postech.ac.kr>wrote:

> Do I need to run make rebuild_cache or just make –j4? I already deleted
> everything under the building directory.
>

If you deleted everything and ran ccmake / cmake again then just make -j4
should be good.


> ****
>
> ** **
>
> *From:* Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com]
> *Sent:* Friday, August 30, 2013 11:33 PM
>
> *To:* Xiaopeng Yang
> *Cc:* ves at public.kitware.com
> *Subject:* Re: [Ves] Errors during VES building using make -j4****
>
> ** **
>
> If you already done git fetch, then do git reset --hard origin/master like
> show below:****
>
> ** **
>
> > git fetch ****
>
> > git checkout master****
>
> > git reset --hard origin/master****
>
> ** **
>
> On Fri, Aug 30, 2013 at 10:31 AM, Xiaopeng Yang <yxp233 at postech.ac.kr>
> wrote:****
>
> Hi Ashish,****
>
>  ****
>
> After I tried git checkout master, a message appeared: Already on
> ‘master’ Your branch is behind ‘origin/master’ by 6 commits, and can be
> fast-forwarded. ****
>
>  ****
>
> Shall I skip this and do git reset --hard origin/master?****
>
>  ****
>
> Thanks,****
>
> Xiaopeng****
>
>  ****
>
> *From:* Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com]
> *Sent:* Friday, August 30, 2013 11:24 PM****
>
>
> *To:* Xiaopeng Yang
> *Cc:* ves at public.kitware.com
> *Subject:* Re: [Ves] Errors during VES building using make -j4****
>
>  ****
>
> No you don't need that just the IOS one should work. Also, after you do
> what I said in my previous email: ****
>
>  ****
>
> Make sure to run: ****
>
>  ****
>
> make rebuild_cache****
>
>  ****
>
> Thanks, ****
>
> Aashish****
>
>  ****
>
>  ****
>
> On Fri, Aug 30, 2013 at 10:18 AM, Xiaopeng Yang <yxp233 at postech.ac.kr>
> wrote:****
>
> Also do I need to turn on VES_HOST_SUPERBUILD?****
>
>  ****
>
> *From:* Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com]
> *Sent:* Friday, August 30, 2013 10:47 PM****
>
>
> *To:* Xiaopeng Yang
> *Cc:* ves at public.kitware.com
> *Subject:* Re: [Ves] Errors during VES building using make -j4****
>
>  ****
>
> Ok, this makes it clear. You need to TURN ON the VES_USE_CURL in the cmake
> / ccmake  / cmake-gui as the KiwiViewer needs it. ****
>
>  ****
>
> So please do this: ****
>
>  ****
>
> > cd your_build_dir_the_top_level****
>
> > ccmake .****
>
> > VES_USE_CURL ON****
>
> > VES_USE_LIBARCHIVE ON****
>
>  ****
>
> Let us know, how it goes. *Also, Would you mind pulling latest changes?
> We pushed a fix that may solve the makeFrameworks.sh problem you run into
> before. For that, do this: *****
>
>  ****
>
> > cd your_ves_source_dir****
>
> > git fetch ****
>
> > git checkout master****
>
> > git reset --hard origin/master****
>
>  ****
>
> Thanks,****
>
> Aashish****
>
>  ****
>
>  ****
>
> On Fri, Aug 30, 2013 at 8:43 AM, Xiaopeng Yang <yxp233 at postech.ac.kr>
> wrote:****
>
> Hi Chaudhary,****
>
>  ****
>
> Enclosed please find the file "vesKiwiOptions.h". Thank you very much.****
>
>  ****
>
> Best,****
>
> Xiaopeng****
>
>  ****
>
> *From:* Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com]
> *Sent:* Wednesday, August 28, 2013 11:38 PM****
>
>
> *To:* Xiaopeng Yang
> *Cc:* ves at public.kitware.com
> *Subject:* Re: [Ves] Errors during VES building using make -j4****
>
>  ****
>
> Can you send me this file "vesKiwiOptions.h". Look for this file in the
> build tree. ****
>
>  ****
>
> Thanks,****
>
>  ****
>
>  ****
>
> On Tue, Aug 27, 2013 at 9:38 PM, Xiaopeng Yang <yxp233 at postech.ac.kr>
> wrote:****
>
> Thank you very much! Now I am debugging KiwiViewer using Xcode. But I get
> errors like: vesKiwiCurlDownloader.h file not found. Could you please let
> me know how to solve this problem?****
>
>  ****
>
> Thanks,****
>
> Xiaopeng****
>
>  ****
>
> *From:* Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com]
> *Sent:* Wednesday, August 28, 2013 6:26 AM****
>
>
> *To:* Xiaopeng Yang
> *Cc:* ves at public.kitware.com
> *Subject:* Re: [Ves] Errors during VES building using make -j4****
>
>  ****
>
>  ****
>
> On Tue, Aug 27, 2013 at 2:56 PM, Xiaopeng Yang <yxp233 at postech.ac.kr>
> wrote:****
>
> Hi ****
>
>  ****
>
> I tried make –j1 as you suggested. And no error occurred. I have another
> question. In step 4 of creating a symlink, do I need to go to Apps/iOS
> directory using $ cd <ves src dir>/Apps/iOS and then run $ ln –s <build
> dir>/CMakeExternals/Install/frameworks ./frameworks?****
>
>  ****
>
> Yes, this is also mentioned in the README.txt for Apps/iOS****
>
>  ****
>
>  ****
>
>  ****
>
> Thanks,****
>
> Xiaopeng****
>
>  ****
>
> *From:* Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com]
> *Sent:* Wednesday, August 28, 2013 2:58 AM****
>
>
> *To:* Xiaopeng Yang
> *Cc:* ves at public.kitware.com
> *Subject:* Re: [Ves] Errors during VES building using make -j4****
>
>  ****
>
> Thanks, can you run ****
>
>  ****
>
> > make -j1****
>
>  ****
>
> Also, what is your git SHA>? ****
>
>  ****
>
> I am not seeing anything obvious in the cache. ****
>
>  ****
>
> Thanks****
>
>  ****
>
>  ****
>
> On Tue, Aug 27, 2013 at 1:49 PM, Xiaopeng Yang <yxp233 at postech.ac.kr>
> wrote:****
>
> Hi Chaudhary,****
>
>  ****
>
> I was trying to build VES for iOS app development by following the
> instruction in README.txt under VES/Apps/iOS. The make –j4 is the 3rdstep in that instruction file.
> ****
>
> Attached is the CMakeCache.txt file. By the way, I was at the very
> beginning stage of VES.****
>
>  ****
>
> Thanks,****
>
> Xiaopeng****
>
>  ****
>
> *From:* Aashish Chaudhary [mailto:aashish.chaudhary at kitware.com]
> *Sent:* Wednesday, August 28, 2013 2:32 AM
> *To:* Xiaopeng Yang
> *Cc:* ves at public.kitware.com
> *Subject:* Re: [Ves] Errors during VES building using make -j4****
>
>  ****
>
> I have not seen this error before. What branch of VES you are tying to
> build? Also can you send us your CMakeCache.txt? ****
>
>  ****
>
> Thanks****
>
>  ****
>
>  ****
>
> On Tue, Aug 27, 2013 at 1:15 PM, Xiaopeng Yang <yxp233 at postech.ac.kr>
> wrote:****
>
> Dear VES users,****
>
>  ****
>
> After I built VES using make –j4, I got two errors. Could anyone let me
> know why these errors occurred?****
>
>  ****
>
> [ 71%] Built target vtk-ios-device****
>
> Scanning dependencies of target ves-ios-device****
>
> Scanning dependencies of target vtk-framework****
>
> [ 75%] [ 75%] -- The CXX compiler identification is GNU 4.2.1****
>
> Creating vtk framework****
>
> Creating directories for 'ves-ios-device'****
>
> make[2]: /Applications/ToolBox/VES/VES/CMake/makeFramework.sh: No such
> file or directory****
>
> make[2]: *** [CMakeFiles/vtk-framework] Error 1****
>
> make[1]: *** [CMakeFiles/vtk-framework.dir/all] Error 2****
>
> make[1]: *** Waiting for unfinished jobs....****
>
>  ****
>
> Thank you very much in advance.****
>
>  ****
>
> Best regards,****
>
> Xiaopeng Yang****
>
>  ****
>
>  ****
>
> _______________________________________________
> Ves mailing list
> Ves at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/ves****
>
>
>
> ****
>
>  ****
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com    ****
>
>
>
> ****
>
>  ****
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com    ****
>
>
>
> ****
>
>  ****
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com    ****
>
>
>
> ****
>
>  ****
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com    ****
>
>
>
> ****
>
>  ****
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com    ****
>
>
>
> ****
>
>  ****
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com    ****
>
>
>
> ****
>
> ** **
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com    ****
>



-- 
| Aashish Chaudhary
| R&D Engineer
| Kitware Inc.
| www.kitware.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20130830/dba5f5ad/attachment-0001.html>