Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
IMPORTANT - Issue tracking has been migrated to JIRA - use your github ID and password reset mechanism to log in
C++ ECL JavaScript XSLT CMake Bison Other
branch: candidate-3.10…

This branch is 7366 commits behind master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
build_utils
cmake_modules
common
dali
deploy
deployment
docs
ecl
ecllibrary
esp
githooks
initfiles
lib2
plugins
roxie
rtl
services
system
testing
thorlcr
tools
.gitattributes
.gitignore
CMakeLists.txt
CNAME
CONTRIBUTORS
FUTURE
LICENSE.txt
README
VERSIONS
baseaddr.txt
build-config.h.cmake
sourcedoc.xml
version.cmake

README

HPCC SYSTEMS software Copyright (C) 2012 HPCC Systems.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
 

http://hpccsystems.com
 

To build for Linux:
-------------------

1. Check out sources (for example, to directory ~/hpcc)
2. Create a build directory - either as a child of hpcc or elsewhere
3. cd to the build directory
4a.To create makefiles to build native release version for local machine, run
cmake ~/hpcc
4b.To create makefiles to build native debug version, run
cmake -DCMAKE_BUILD_TYPE=Debug ~/hpcc
4c.To create makefiles to build 32-bit version from 64-bit host, run
cmake -DCMAKE_C_FLAGS:STRING="-m32 -march=i386" -DCMAKE_CXX_FLAGS:STRING="-m32 -march=i386" ~/hpcc
5. To build the makefiles just created above, run
make
6. Executables will be created in ./<releasemode>/bin and ./<releasemode>/libs
7. To create a .deb / ,rpm to install, run
make package

 
To build for Windows:
---------------------

1. Check out sources (for example, to directory c:\hpcc)
2. Create a build directory - either as a child of hpcc or elsewhere
3. cd to the build directory
4. To create a Visual Studio project, run
cmake c:\hpcc -G "Visual Studio 9 2008"
The sln file hpccsystems-platform.sln will be created in the current directory, and will support debug and release targets
5. To build the project, load the solution into the visual studio IDE and build in the usual way.
6. Executables will be created in (for example) c:\hpcc\bin\<release_mode>

To build client tools for Macintosh OSX:
----------------------------------------

1. Check out sources (for example, to directory ~/hpcc)
2. You many need to install some 3rd-party dev packages using macports
3. Create a build directory - either as a child of hpcc or elsewhere
4. cd to the build directory
5. Use clang to build the clienttools (gcc4.2 cores when compiling some of the sources):
CC=/usr/bin/clang CXX=/usr/bin/clang++ cmake ~/hpcc -DCLIENTTOOLS_ONLY
5. To build the makefiles just created above, run
make
6. Executables will be created in ./<releasemode>/bin and ./<releasemode>/libs
7. To create a .dmg to install, run
make package
 
 
Something went wrong with that request. Please try again.