Skip to content
This repository has been archived by the owner on Jan 10, 2018. It is now read-only.

Commit

Permalink
add make targets + build instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
devernay committed Sep 2, 2015
1 parent 59ab583 commit f62a96b
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 12 deletions.
37 changes: 26 additions & 11 deletions README.md
Expand Up @@ -43,22 +43,37 @@ In order to get a specific tag, corresponding to a source release, do `git tag -
to get the list of tags, and then `git checkout tags/<tag_name>`
to checkout a given tag.

### Unix/Linux/FreeBSD/OS X, using Makefiles
### Compiling (Unix/Linux/FreeBSD/OS X, using Makefiles)

To compile an optimized version for a 64-bits machine: open a shell in
the toplevel directory, and type
On Unix-like systems, the plugins can be compiled by typing in a
terminal:
- `make [options]` to compile as a single combined plugin (see below
for valid options).
- `make nomulti [options]` to compile as separate plugins (useful if
only a few plugins are is needed, for example). `make` can also be
executed in any plugin's directory.

make DEBUGFLAG=-O3 BITS=64
The most common options are `CONFIG=release` to compile a release
version, `CONFIG=debug` to compile a debug version. Or
`CONFIG=relwithdebinfo` to compile an optimized version with debugging
symbols.

Without the DEBUGFLAG flag, a debug version will be compiled, and use
BITS=32 to compile a 32-bits version.
Another common option is `BITS=32`for compiling a 32-bits version,
`BITS=64` for a 64-bits version, and `BITS=Universal` for a universal
binary (OS X only).

The compiled plugins will be placed in subdiecories named after the
See the file `Makefile.master`in the toplevel directory for other useful
flags/variables.

The compiled plugins are placed in subdirectories named after the
configuration, for example Linux-64-realease for a 64-bits Linux
compilation. In each of these directories, you will find a `*.bundle`
file, which has to be moved to the proper place (`/usr/OFX/Plugins`on
Linus, or `/Library/OFX/Plugins`on OS X), using a command like:
sudo mv */*/*.bundle /usr/OFX/Plugins
compilation. In each of these directories, a `*.bundle` directory is
created, which has to be moved to the proper place
(`/usr/OFX/Plugins`on Linux, or `/Library/OFX/Plugins`on OS X), using
a command like the following, with the *same* options used for
compiling:

sudo make install [options]

### OS X, using Xcode

Expand Down
2 changes: 1 addition & 1 deletion openfx

0 comments on commit f62a96b

Please sign in to comment.