Skip to content

Commit

Permalink
Change html spans left over from website migration to gui styling again
Browse files Browse the repository at this point in the history
  • Loading branch information
Apanatshka committed May 31, 2024
1 parent 9f0b2a6 commit 3176595
Show file tree
Hide file tree
Showing 6 changed files with 103 additions and 103 deletions.
4 changes: 2 additions & 2 deletions content/howtos/development/build-spoofax.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ The `-s` flag build Stratego/XT instead of downloading it, and `-t` skips the St
Use `.\bd.bat build` to get a list of components available for building, and `.\bd.bat build --help` for help on all the command-line flags and switches.

!!! warning ""
If you have opened a project in the repository in Eclipse, you **must turn off** _Project__Build Automatically_ in Eclipse, otherwise the Maven and Eclipse compilers will interfere and possibly fail the build. After the Maven build is finished, enable _Build Automatically_ again.
If you have opened a project in the repository in Eclipse, you **must turn off** `#!gui Project > Build Automatically` in Eclipse, otherwise the Maven and Eclipse compilers will interfere and possibly fail the build. After the Maven build is finished, enable `#!gui Build Automatically` again.


## Updating the Source Code
Expand Down Expand Up @@ -180,4 +180,4 @@ If updating or checking out a branch of submodule fails (because of unstaged or
Resetting and cleaning **deletes uncommitted and unpushed changes**, which can cause **permanent data loss**. Make sure all your changes are committed _and_ pushed!

### Weird Compilation Errors
If you get any weird compilation errors during the command-line build, make sure that _Project__Build Automatically_ is turned off in Eclipse.
If you get any weird compilation errors during the command-line build, make sure that `#!gui Project > Build Automatically` is turned off in Eclipse.
22 changes: 11 additions & 11 deletions content/howtos/development/develop-spoofax.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,26 +38,26 @@ This will download and install Eclipse into `~/eclipse/spoofax-dev` with the rig
### Fixing Eclipse Settings
Some Eclipse settings unfortunately have sub-optimal defaults. Go to the Eclipse preferences and set these options:

- General
- `#!gui General`
- **Enable**: Keep next/previous editor, view and perspectives dialog open
- General Startup and Shutdown
- `#!gui General > Startup and Shutdown`
- **Enable**: Refresh workspace on startup
- General Workspace
- `#!gui General > Workspace`
- **Enable**: Refresh using native hooks or polling
- Maven
- `#!gui Maven`
- **Enable**: Do not automatically update dependencies from remote repositories
- **Enable**: Download Artifact Sources
- **Enable**: Download Artifact JavaDoc
- Maven Annotation Processing
- `#!gui Maven > Annotation Processing`
- **Enable**: Automatically configure JDT APT
- Maven User Interface
- `#!gui Maven > User Interface`
- **Enable**: Open XML page in the POM editor by default
- Run/Debug Launching
- `#!gui Run/Debug > Launching`
- **Disable**: Build (if required) before launching


### Developing
Import the projects you’d like to develop. To import Java and language projects, use _Import ‣ Maven Existing Maven Projects_. Eclipse plugins are still imported with _Import ‣ General Existing Projects into Workspace_.
Import the projects you’d like to develop. To import Java and language projects, use `#!gui Import > Maven > Existing Maven Projects`. Eclipse plugins are still imported with `#!gui Import > General > Existing Projects into Workspace`.


### Running
Expand All @@ -70,13 +70,13 @@ Some tricks:


### Troubleshooting
If launching the guest Eclipse does not work due to a missing JavaSE-11, you need to register a Java 11 compatible JRE. Go to _Preferences__Java__Installed JREs_, and click the Add... button, and find the install directory of your Java 11 compatible JRE. For example, when you've installed Java 11 with SDKMAN, it may be at `~/.sdkman/candidates/java/11.0.13-tem`.
If launching the guest Eclipse does not work due to a missing JavaSE-11, you need to register a Java 11 compatible JRE. Go to `#!gui Preferences > Java > Installed JREs`, and click the `#!gui Add...` button, and find the install directory of your Java 11 compatible JRE. For example, when you've installed Java 11 with SDKMAN, it may be at `~/.sdkman/candidates/java/11.0.13-tem`.

If there are many errors in a project, try updating the Maven project. Right click the project and choose _Maven__Update Project..._, uncheck _Clean projects_ in the new dialog and press _OK_. This will update the project from the POM file, update any dependencies, and trigger a build. If this does not solve the problems, try it again but this time with _Clean projects_ checked. Note that if you clean a language project, it has to be rebuilt from the command-line. Restarting Eclipse and repeating these steps may also help.
If there are many errors in a project, try updating the Maven project. Right click the project and choose `#!gui Maven > Update Project...`, uncheck `#!gui Clean projects` in the new dialog and press `#!gui OK`. This will update the project from the POM file, update any dependencies, and trigger a build. If this does not solve the problems, try it again but this time with `#!gui Clean projects` checked. Note that if you clean a language project, it has to be rebuilt from the command-line. Restarting Eclipse and repeating these steps may also help.

Multiple projects can be updated by selecting multiple projects in the package/project explorer, or by checking projects in the update dialog.

If you have particular trouble with `org.eclipse.*` plugins in the `MANIFEST.MF` file that do not resolve, try the following. Go to _Preferences__Plug-in Development__Target Platform_, most likely there will not be an active _Running Platform_ there. You can use _Add..._ to add a new one if there isn’t one already. Select the _Default_ option, click _Next_, then click _Finish_. Check the box next to the platform to activate it.
If you have particular trouble with `org.eclipse.*` plugins in the `MANIFEST.MF` file that do not resolve, try the following. Go to `#!gui Preferences > Plug-in Development > Target Platform`, most likely there will not be an active _Running Platform_ there. You can use `#!gui Add...` to add a new one if there isn’t one already. Select the _Default_ option, click `#!gui Next`, then click `#!gui Finish`. Check the box next to the platform to activate it.


### Advanced: Developing from Scratch
Expand Down
4 changes: 2 additions & 2 deletions content/howtos/development/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ The path /var/folders/a_/foo0000bar/T/vfs_cache-345/tmp_123_macosx/sdf2table-mac
is not shared from the host and is not known to Docker.
```

Ensure the root of the path (`/var/folders` in this example) is shared in Docker for Mac. Go to Docker for Mac _Preferences__Resources__File Sharing_ and add the path to the list. The default list should contain:
Ensure the root of the path (`/var/folders` in this example) is shared in Docker for Mac. Go to Docker for Mac `#!gui Preferences > Resources > File Sharing` and add the path to the list. The default list should contain:

- `/Users`
- `/Volumes`
Expand All @@ -125,4 +125,4 @@ bind source path does not exist:
/var/folders/a_/foo0000bar/T/vfs_cache-345/tmp_123_macosx
```

Ensure that both Docker and the terminal from which you are invoking the build have _full-disk access_. Go to macOS _Preferences__Security and Privacy__Full Disk Access_ and check the checkboxes next to _Docker_ and your terminal (_Terminal_ and/or _iTerm_).
Ensure that both Docker and the terminal from which you are invoking the build have _full-disk access_. Go to macOS `#!gui Preferences > Security and Privacy > Full Disk Access` and check the checkboxes next to _Docker_ and your terminal (_Terminal_ and/or _iTerm_).
2 changes: 1 addition & 1 deletion content/howtos/statix/migrating-to-concurrent-solver.md
Original file line number Diff line number Diff line change
Expand Up @@ -190,7 +190,7 @@ a library. These libraries can be linked with other projects, potentially
decreasing analysis times significantly. Statix libraries can be generated and
linked by following three steps.

As a first step, use the `#!gui Spoofax Statix Make project library` menu on
As a first step, use the `#!gui Spoofax > Statix > Make project library` menu on
a file in your library project to export its scope graph. A `project.stxlib`
file will now appear in the root directory of that project.

Expand Down
Loading

0 comments on commit 3176595

Please sign in to comment.