Skip to content

Commit

Permalink
Always use junctions for manual setup, Remove redundant steps - compl…
Browse files Browse the repository at this point in the history
…ements #3652
  • Loading branch information
jonpas committed Apr 3, 2016
1 parent 837ed44 commit b2c34be
Showing 1 changed file with 3 additions and 16 deletions.
19 changes: 3 additions & 16 deletions wiki/development/setting-up-the-development-environment.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,26 +41,13 @@ After ensuring that you have installed all requirements, execute the `setup.py`

### 4.1 Manual Setup

Should the script fail, here is how you create the required links manually:

First, to set up the links, create `z` folders both in your Arma 3 directory and on your P-drive. Then run the following commands as admin, replacing the text in brackets with the appropriate paths:

Windows 8:
Should the script fail, here is how you create the required links manually. Run the following commands as admin, replacing the text in brackets with the appropriate paths:

```sh
mklink /D /J "[Arma 3 installation folder]\z\ace" "[location of the ACE3 project]"
mklink /D /J "P:\z\ace" "[location of the ACE3 project]"
mklink /J "[Arma 3 installation folder]\z\ace" "[location of the ACE3 project]"
mklink /J "P:\z\ace" "[location of the ACE3 project]"
```

Windows 7 and Vista:

```sh
mklink /D "[Arma 3 installation folder]\z\ace" "[location of the ACE3 project]"
mklink /D "P:\z\ace" "[location of the ACE3 project]"
```

Then, copy the `cba` folder from the `tools` folder to `P:\x\cba`. Create the `x` folder if needed. That folder contains the parts of the CBA source code that are required for the macros to work.


## 5. Creating a Test Build

Expand Down

0 comments on commit b2c34be

Please sign in to comment.