I got to the step to build opensync, and that failed: [fher...@fluffy play]$ ./build1 CMake Error: The source directory "/home/fherman/rpms/play/opensync/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. CMake Error: The source directory "/home/fherman/rpms/play/osynctool/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. CMake Error: The source directory "/home/fherman/rpms/play/evolution2/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. CMake Error: The source directory "/home/fherman/rpms/play/vformat/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. CMake Error: The source directory "/home/fherman/rpms/play/xmlformat/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI.
Note that I used a directory /home/fherman/rpms/play and adjusted the environment accordingly. I assumed that "rootdir" was not a placeholder name but the literal name. The build directories in the above were empty. I also placed the build instructions for the Build opensync part of your instruction in an executable file build1 in the play directory, and then executed it while in the play directory. Fred Chris Frey wrote: > On Wed, Apr 08, 2009 at 07:22:24PM -0600, Frederic Herman wrote: >> I have libopensync version 0.36-3.fc10 >> >> I'm willing to try to build the required packages, but I would need help >> doing it since I am unfamiliar with the process. I don't even know what >> packages I would be building or where to get the source from. >> >> So if you want to help me through it, I'll try it. > > Great! > > First of all, the obligatory pointer to the documentation :-) > http://www.netdirect.ca/software/packages/barry/ > > That is geared for version 0.14, but still pretty useful. It will be > updated with 0.15 docs soon when we make a new release. > > If you are using YUM, install the following: > > yum install \ > autoconf automake libtool gcc g++ libusb-devel \ > pkg-config \ > sqlite3 cmake glib2 libxml2-devel > > That was off the top of my head, so the names of packages may be a little > off. This is a first start... if we missed any dependencies, we'll find > it in the build process. > > Next, I recommend you use git to grab the latest Barry sources. > > yum install git > > It might be called "git-core" on your system. > > Install SVN for opensync: > > yum install svn > > Next, pick a directory for your Barry sources: > > mkdir ~/play > cd ~/play > git clone git://repo.or.cz/barry.git barry > > Grab the latest opensync sources: > > svn co http://svn.opensync.org/trunk opensync > svn co http://svn.opensync.org/osynctool/trunk osynctool > svn co http://svn.opensync.org/plugins/evolution2 evolution2 > svn co http://svn.opensync.org/format-plugins/vformat vformat > svn co http://svn.opensync.org/format-plugins/xmlformat/trunk xmlformat > > Setup your environment: > > export PKG_CONFIG_PATH=/home/you/play/rootdir/lib/pkgconfig > export OSYNC_TRACE=/home/you/play/trace_logs > mkdir /home/you/play/trace_logs > export LD_LIBRARY_PATH=/home/you/play/rootdir/lib > > > Build opensync: > > rm -rf rootdir > for f in opensync osynctool evolution2 vformat xmlformat ; do > (cd $f && rm -rf build && mkdir build && cd build && \ > cmake -DCMAKE_INSTALL_PREFIX=/home/you/play/rootdir && \ > make && make install) > done > > > Build Barry: > > cd ~/play/barry > ./buildgen.sh > ./configure --prefix=/home/you/play/rootdir --enable-opensync-plugin-4x > make > make install > > > You don't need to be root for any of the above. > > At this point you can run osynctool from your own ~/play/rootdir/bin > directory. > Do the usual --addgroup, --addmember, --configure, --discover, --sync > steps from the command line, making sure to run 'evolution --force-shutdown' > between --discover and --sync, and before each new --sync. > > If you run into build errors, just paste the whole screenful of text and > we'll work it out. :-) > > Thanks! > - Chris > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel > ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
