forked from hpcc-systems/HPCC-Platform
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
65 lines (50 loc) · 2.53 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
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