Artistic Style - Install Information

# Artistic Style Install Information

### Contents

Artistic Style Versions

Linux Version

CodeBlocks Linux

GCC Makefile

Clang Makefile

Intel Makefile

Other Makefile Targets

MacOS Version

Xcode

MacOS Makefile

Windows Version

Precompiled Executable

CodeBlocks Windows

Visual Studio

Other Development Environments

Compiler Options

### Artistic Style Versions

astyle_x.x_linux.tar.gz is the Linux version of Artistic Style. It contains the source code, documentation, and makefiles. The Linux Version compile instructions below give information for compiling the source code.

astyle_x.x_macos.tar.gz is the Mac OS version of Artistic Style. It contains the source code, documentation, Xcode project files, and a makefile. The Mac OS Version compile instructions below give information for compiling the source code.

astyle_x.x_windows.zip is the Windows version of Artistic Style. It contains the source code, documentation, Visual C project files, and an executable. The Windows Version compile instructions below give information for compiling the source code.

Only one platform is supported in each distribution package. If you use Artistic Style on more than one platform you will need to download packages for each platform. The main difference in platforms is the build directories and the line endings. Most compilers and development packages will accept any type of line ending. The source code and documentation are the same for all distributions.

### Linux Version

#### CodeBlocks Linux

There are build folders for the following compilers. All compiler folders are in the "build" directory.

- cb-clang contains the workspace and project files for the Linux Clang Compiler.
- cb-gcc contains the workspace and project files for the Linux GCC Compiler.
- cb-intel contains the workspace and project files for the Linux Intel Compiler.

There are workspace and project files for each folder. All projects have at least Debug and Release configurations. All output will be in the "bin" directory.

The workspace contains the following projects.

- AStyle builds the Artistic Style command line program (astyle).
- AStyle So builds the Artistic Style program as a shared object (libastyle.so).
- AStyle Java builds the Artistic Style program as a shared object (libastylej.so) that can be called from a Java program. The Java Development Kit (JDK) is required for the project to compile. The Project Properties must have an include path to the JDK include directories.
- AStyle A builds the Artistic Style program as a Static Library (libastyle.a). This can be statically linked to a user program.

For other Linux development environments, follow the instructions in Other Development Environments.

#### GCC Makefile

To compile using the GCC compiler you must have GCC (3.1 or better) installed.

The build has no autoconf dependency. To build the Artistic Style configurations, use the makefile located in the astyle/build/gcc directory. The executables will be in the astyle/build/gcc/bin directory. To build the command line configuration, enter the following:

    cd astyle/build/gcc
    make

To build the other astyle configurations, you can enter the file name or a symbolic name. Entering "make astyle" or "make release" will build the command line configuration. Following are the symbolic names and file names (in parens) of the various configurations:

- release or astyle builds the Artistic Style command line program. This is the default option.
- shared or libastyle.so builds the Artistic Style program as a shared library.
- static or libastyle.a builds the Artistic Style program as a static library.
- debug or astyled builds the Artistic Style command line program with debugging information
- shareddebug or libastyled.so builds the Artistic Style program as a shared library with debugging information.
- staticdebug or libastyled.a builds the Artistic Style program as a static library with debugging information.
- all builds all the above configurations.

  The following Java shared library builds are separate from the above. They include a Java Native Interface (JNI) and require that the Java Development Kit (JDK) be installed. The environment variable JAVA_HOME should be defined. It defines the install directory for the JDK. The makefile also has default install directories for Java 5 and 6. If the compile cannot find the file jni.h, either set the variable or change the value in the makefile.

- java builds the Artistic Style program as a shared library which includes the JNI (libastylej.so).
- javadebug builds the Artistic Style program as a shared library which includes the JNI and debugging information (libastylejd.so).
- javaall builds all the above java configurations.

More than one configuration can be built at the same time. For example, to build all the release configurations enter:

    cd astyle/build/gcc
    make release shared static

The Other Makefile Targets section contains additional target options.

#### Clang Makefile

Clang has a static analyzer that finds potential bugs in C/C++ and Objective-C programs. It can be run as a standalone tool from the command-line, and runs in tandem with a build. There is a script file, analyze.sh, that will run the analysis on Artistic Style.

The build has no autoconf dependency. To build the Artistic Style configurations use the makefile located in the astyle/build/clang directory. The executables will be in the astyle/build/clang/bin directory. To build the command line configuration, enter the following:

    cd astyle/build/clang
    make

To build the other astyle configurations, you can enter the file name or a symbolic name. The configurations for Clang are the same as for the GCC Makefile. More than one configuration can be built at the same time. For example, to build all the release configurations enter:

    cd astyle/build/clang
    make release shared static

The Other Makefile Targets section contains additional target options.

#### Intel Makefile

These procedures and the makefile are for recent versions of the compiler. They may not work for earlier versions. Instructions for your compiler are in the compiler documentation file "get_started_lc.htm".

To compile with Intel there are environment variables that must be set by running the compiler environment script compilervars.sh (or compilervars.csh) with an argument that specifies the target architecture. This should be done before running the make. If it is not done, "make" will display an error message stating that the compiler environment variables are not set.

The build has no autoconf dependency. To build the Artistic Style configurations use the makefile located in the astyle/build/intel directory. The output executables will be in the astyle/build/intel/bin directory. To build the command line configuration, enter the following:

    cd astyle/build/intel
    make

To build the other astyle configurations, you can enter the file name or a symbolic name. The configuration names for Intel are the same as for the GCC Makefile. More than one configuration can be built at the same time. For example, to build the entire debug configurations enter:

    cd astyle/build/intel
    make debug shareddebug staticdebug

The Other Makefile Targets section contains additional target options.

#### Other Makefile Targets

The following makefile targets are available for GCC, Clang, Intel, and Mac.

##### clean

Removes the object and executable files for all configurations.

To remove the files for all configurations:

    make clean

##### cleanobj

Removes the object files for all configurations. The executables will not be removed.

To remove only the object files for all configurations:

    make cleanobj

##### install

Installs the astyle executable and documentation files. The default is /usr/bin for the executable and /usr/share/doc/astyle for the documentation. You must have the appropriate permissions to use install.

To install the astyle to the default directories:

    sudo make install

To install astyle to a different bin directory set a value for the macro $(prefix). For example, to install the executable to a user's home directory (/home/user/bin):

    sudo make prefix=$HOME install

##### uninstall

Uninstalls the executable and documentation. You must have the appropriate permissions to use uninstall.

To uninstall astyle from the default directories:

    sudo make uninstall

To uninstall the files from a different directory set a value for the macro $(prefix). For example, to uninstall the files from a user's home directory (/home/user):

     sudo make prefix=$HOME uninstall

NOTE: The uninstall option will NOT remove the .astylerc files from the users' home directories. The files must be removed individually for each user.

### MacOS Version

#### Xcode

Artistic Style workspace and project files for the Xcode development environment are available in the "build/xcode" directory. A workspace can be used to build a single project or all the projects. The project files have Debug and Release configurations. The following projects are available.

- AStyle builds the Artistic Style command line program (astyle).
- AStyleA builds the Artistic Style program as a Static Library (libastyle.a). This can be statically linked with an executable.
- AStyleDylib builds the Artistic Style program as a Dynamic Library (libastyle.dylib). It can be used with C/C++, Objective C, C#, and Python programs.
- AStyleJava builds the Artistic Style program as a Dynamic Library (libastylej.dylib) that can be called from a Java program. The Java Development (JDK) is required for the project to compile. The Project Properties must have an include path to the JDK include directory. The output dylib can also be called from a C++ or C# program.

##### install

Only the astyle executable is installed. The library project installs are sent to UninstalledProjects in the Build directory. The following instructions are for the astyle executable and documentation files. The default install directory is /usr/bin for the executable and /usr/share/doc/astyle for the documentation. You must have the appropriate permissions to use install. If sudo is not used for the install, an error will occur during the build.

To install the astyle executable in the default directory:

    cd astyle/build/xcode
    sudo xcodebuild install -project AStyle.xcodeproj

A script is used to install the documentation from the same directory.

    sudo bash install.sh

##### uninstall

Uninstalls the executable and documentation. You must have the appropriate permissions to use uninstall.

A script is used to uninstall astyle and the documentation:

    sudo bash uninstall.sh

NOTE: The uninstall option will NOT remove the .astylerc files from the users' home directories. The files must be removed individually for each user.

#### MacOS Makefile

The Artistic Style makefile compile uses the Mac OS "Command Line Tools". If you have Xcode 4.3 or newer the command line tools, such as "make", are NOT installed by default. They must be downloaded and installed separately. Once everything is successfully installed, you should see "make" and other command line developer tools in /usr/bin.

The build has no autoconf dependency. To build the Artistic Style configurations use the makefile located in the astyle/build/mac directory. The executables will be in the astyle/build/mac/bin directory. To build the command line configuration, enter the following:

    cd astyle/build/mac
    make

To build the other astyle configurations, you can enter the file name or a symbolic name. The configurations for Mac are the same as for the GCC Makefile. More than one configuration can be built at the same time. For example, to build all the release configurations enter:

    cd astyle/build/mac
    make release shared static

The Other Makefile Targets section contains additional target options.

### Windows Version

#### Precompiled Executable

In addition to the source files, the Windows distribution package contains an Artistic Style Win32 executable (AStyle.exe). If you prefer to compile the executable yourself, pursue the following instructions.

#### CodeBlocks Windows

There are build folders for the following compilers. All compiler folders are in the "build" directory.

- cb-bcc32c contains the workspace and project files for the Embarcadero BCC32C Compiler.
- cb-mingw contains the workspace and project files for the MinGw or TDM_GCC Compilers.

There are workspace and project files for each folder. All projects have at least Debug and Release configurations. All output will be in the "bin" directory.

The workspace contains the following projects.

- AStyle builds the Artistic Style command line program (AStyle.exe).
- AStyle Dll builds the Artistic Style program as a shared object (AStyle.dll).
- AStyle Java builds the Artistic Style program as a shared object AStylej.dll) that can be called from a Java program. The Java Development Kit (JDK) is required for the project to compile. The Project Properties must have an include path to the JDK include directories.
- AStyle Lib builds the Artistic Style program as a Static Library (astyle.lib). This can be statically linked to a calling program.

For other development environments, follow the instructions in Other Development Environments.

#### Visual Studio

There are solution and project files for several versions of Microsoft Visual Studio. Open an Artistic Style solution file in the appropriate "build" directory. All projects have Debug, Release and Static configurations. Debug file output will be in the "debug" directory. Release file output will be in the "bin" directory. Static file output will be in the "binstatic" directory. The following solution files are available.

- All AStyle builds the release and the debug configurations for all the following.
- AStyle builds the Artistic Style command line program (AStyle.exe). This project has an extra "Static" option. It is the same as the "Release" build except that it is linked with a static runtime library. This is needed if the executable is to be run on a system without Visual Studio installed. The builds for this configuration are placed in a separate "binstatic" directory.
- AStyle Dll builds the Artistic Style program as a Dynamic Link Library (AStyle.dll). This will also build an export library and a static library for linking the dll.
- AStyle Java builds the Artistic Style program as a Dynamic Link Library (AStylej.dll) that can be called from a Java program. The Java Development (JDK) is required for the project to compile. The Project Properties must have an include path to the JDK include and include/win32 directories. This is set in "Project > Properties > C/C++ > General > Additional Include Directories". The default setting is for the JDK to be installed in the default directory, but it may not be the most current release. The output DLL can also be called from a C++ or C# program.
- AStyle Lib builds the Artistic Style program as a Static Library (libAStyle.lib). This can be statically linked to a calling program.

### Other Development Environments

To use other development environments a project file must be built.

- Create a project using the development environment.
- Add to the project all the .cpp and .h files in the "src" directory.
- The Compiler Options section discusses the compiler options to use.
- Compile.

### Compiler Options

No macro definitions are required to compile the executable. To compile as a static or shared (dynamic) library define the macro ASTYLE_LIB. To compile a Java shared (dynamic) library define the macro ASTYLE_JNI. The option ASTYLE_NO_EXPORTS is sometimes needed for static libraries to prevent compiler error and warning messages. Use the appropriate compiler and linker options to compile the static or shared library. Add debug options to compile the debug versions.

Artistic Style is a small program and it is best to optimize for speed. The debug configurations are not usually optimized. To optimize for speed in the release configurations, use the macro NDEBUG to remove asserts. If necessary, use an option to activate the C++11 standards (-std=c++11 or -std=c++0x on most compilers). Use an option that allows inline function expansion. Runtime Type Information (RTTI) is NOT needed and exceptions are NOT used. Use whole program optimization if your compiler supports it. There may be other options you can use depending on the compiler.