Skip to content

Commit

Permalink
Updated JVM memory defaults
Browse files Browse the repository at this point in the history
  • Loading branch information
SlimerDude committed May 16, 2020
1 parent 47c61b3 commit d7a131a
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 5 deletions.
5 changes: 2 additions & 3 deletions product/com.xored.f4.ide.product
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,8 @@
<programArgs>-showsplash
com.xored.f4.platform
</programArgs>
<vmArgs>-Xms80m
-Xmx512m
-XX:MaxPermSize=128m
<vmArgs>-Xms256m
-Xmx1024m
</vmArgs>
</launcherArgs>

Expand Down
Binary file added product/icons/logo.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 4 additions & 2 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,16 +54,18 @@ Maven is used to package F4, and has been tested with [Maven 3.3.9](http://archi

Eclipse is used to build all the pods and jars. The Maven build just assembles it all into a executables and Eclipse update repositories.

1. Run `mvn -o clean package` in the root directory of the `Fantom Runtime` project.
1. Run `mvn clean package` in the root directory of the `Fantom Runtime` project.
2. Modify `pom.xml` in the F4 project to point to the newly built runtime.
3. Run `mvn -o clean package` in the root directory of the `F4` project.
3. Run `mvn clean package` in the root directory of the `F4` project.

Steps 1 & 2 only need to be done the once.

Step 3 builds F4 as standalone product.

An eclipse update site `.zip` will be assembled the `/repository/target/` folder and full installation products may be found under `/product/target/products/`.

Tip - use `mvn -o clean package` to run offline builds.



## Testing
Expand Down

0 comments on commit d7a131a

Please sign in to comment.