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
branch: master

Merge branch 'candidate-5.2.0'

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
Failed to load latest commit information.
build_utils HPCC-9713 Bad installation message when installing on Ubuntu 13.04
charm HPCC-11289 Add README file for HPCC Juju Charm Development
clienttools HPCC-10526 add testing/regress to platform and clienttools install
cmake_modules HPCC-13047 Redis plugin sync module
common Merge branch 'candidate-5.2.0'
dali Merge pull request #7052 from afishbeck/jsonSprayKind
deploy gh-2562 Change license to Apache
deployment Merge branch 'candidate-5.2.0'
docs HPCC-13139 DOCS:System Admin docs formatting
ecl Merge branch 'candidate-5.2.0'
ecllibrary HPCC-12653 Std.Date should not use %F, %T, %R
esp Merge branch 'candidate-5.2.0'
githooks Merge remote-tracking branch 'origin/candidate-3.10.x'
initfiles Merge pull request #6937 from Michael-Gardner/HPCC-12978_master
lib2 HPCC-9671 Add Published Query Pages
misc HPCC-9508 Add eclipse code layout settings file to project
plugins Merge branch 'candidate-5.2.0'
roxie Merge branch 'candidate-5.2.0'
rtl Merge branch 'candidate-5.2.0'
services HPCC-12622 Deprecate toCharArray()
system Merge branch 'candidate-5.2.0'
testing Merge branch 'candidate-5.2.0'
thorlcr Merge branch 'candidate-5.2.0'
tools Merge branch 'candidate-5.2.0'
.gitattributes Issue #254 Switches template reading to use jlib
.gitignore Minor code cleaup to avoid false positives from Eclipse
.gitmodules HPCC-12805 JavaScript Graph Control
CMakeLists.txt HPCC-12837 Correct clienttools package file name
CNAME Add CNAME entry for GitHub pages redirection
CONTRIBUTORS HPCC-9508 Add eclipse code layout settings file to project
FUTURE Initial version of FUTURE document
LICENSE.txt HPCC-11269 Add Word Cloud Visualisation
README gh-2562 Change license to Apache …
VERSIONS VERSION rules updated
baseaddr.txt HPCC-9494 Clean up unused roxiemanager code
build-config.h.cmake HPCC-9902 Use the build version as the ecl version reported by eclcc
sourcedoc.xml Merge remote-tracking branch 'origin/closedown-4.2.x'
version.cmake Split off candidate-5.2.0 branch

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.