How do I build Veracity from source on Linux?

Question

I 'd like to get a Veracity development environment set up on Ubuntu or Fedora. Can I?

Accepted Answer

Introduction

This document provides instructions to build Veracity on two of the most common Linux distributions (Ubuntu and Fedora). Ubuntu is the distribution used by our Linux-oriented developers, and is the only Linux build we test as the moment. There's nothing specifically preventing you from building Veracity elsewhere, we just don't yet have documentation to help.

If you are running a recent Ubuntu version (9 or above) or the latest Fedora (Fedora 14), and are comfortable installing a few packages, this document should get you on your way to a working Veracity build.

Getting/Unpacking the Source

There are two options.

Download the latest Veracity tarball.

or

Clone the public repository: http://public.veracity-scm.com/repos/veracity. (Note that you won't be able to push to this repository.)

Unpack or checkout in the directory of your choice - for brevity, we'll pretend you unpacked it under ~/v, and so your source tree begins at ~/v/veracity

Prerequisites

Ubuntu Packages

Install packages using apt-get:

sudo apt-get install build-essential cmake curl zlib1g-dev libicu-dev uuid-dev libcurl4-openssl-dev libnspr4-dev unzip

Install the following packages:

build-essential
cmake
curl
zlib1g-dev
libicu-dev
uuid-dev
libcurl4-openssl-dev
libnspr4-dev
unzip (only needed if you want to run the test suite)

Fedora Packages

Install Fedora packages with yum:

sudo yum install cmake gcc gcc-c++ nspr-devel zlib-devel libicu-devel libcurl-devel libuuid-devel

Install the following packages:

cmake
gcc
gcc-c++
nspr-devel
zlib-devel
libicu-devel
libcurl-devel
libuuid-devel

Creating the Build Directory

cmake will handle the creation of Makefiles, etc. You just need to give it a place to work.

For example, let's create a ~/v/debug, a neighbor of our source directory.

cd to this folder, then run:

cmake -G "Unix Makefiles" ../veracity

... or, if you'd also like an Eclipse project:

cmake -G "Eclipse CDT4 - Unix Makefiles" ../veracity

(Installing Eclipse is left as an exercise to the reader.)

Building Veracity

You now have a build tree, replete with Makefiles. You'll only need to run the top-level one. So:

cd ~/v/debug
make

Updating your PATH to find Veracity Command Line Tools

To make your life easier at this point, you'll want to add the following to your PATH:

~/v/debug/src/cmd
~/v/debug/src/script

the homes of vv (the Veracity command-line app) and vscript (the scripting engine), respectively.

Running the Test Suite

To run the test suite:

cd ~/v/debug
make test

All tests should pass. If there are failures, you can consult the logs.

Answer 2

Does not compile for me. This is on a Debian stable ("squeeze"). The error message means nothing to me. Am I supposed to populate this VVTHIRDPARTY directory myself? With what?

~/tmp/v % cmake -G "Unix Makefiles" ../veracity 
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Machine Type: i686
-- Found vv-thirdparty path: /home/stephane/tmp/veracity/../vv-thirdparty/i686
CMake Error at CMakeLists.txt:124 (MESSAGE):
  Missing or invalid VVTHIRDPARTY directory.  Set cmake variable VVTHIRDPARTY
  to point to 'vv-thirdparty/<architecture>'.

-- Configuring incomplete, errors occurred!

Answer 3

1

Be carefull, with gcc 4.6, the -Werror causes a build fail, because of variable ‘*’ set but not used [-Wunused-but-set-variable]

I removed the -Werror, and everything went well

link

answered Jul 20 '11 at 03:08

judu
16●2

The GCC 4.6 errors have since been resolved.

(Aug 15 '11 at 09:40) Paul Roub ♦♦

concretely speaking, remove the option '-Wall' from '~/v/veracity/common-CMakeLists.txt'

(Oct 04 '11 at 12:17) Takayuki Goto

Answer 4

Still doesn't build out-of-the-box on Fedora 15. Here are my updated workaround instructions:

To solve the spidermonkey build issue:

cd /usr/include

su -c 'ln -s nspr{4,}'
To help CMake find the built copy of spidermonkey, from the build dir (only needed on x86):

cd ../vv-thirdparty/

ln -s i686/ i386
To prevent the build failing due to warnings being treated as errors, edit ../veracity/common-CMakeLists.txt and remove the word -Werror from the line that begins with "set(CMAKE_C_FLAGS".