Project

General

Profile

Revision 507da95d

View differences:

README.md
164 164
```
165 165
$ autoconf
166 166
$ ./configure
167
configure: Git branch: {CURRENT_GIT_BRANCH}
168
configure: ******** Configuration ********
169
configure: bin path:     NONE/bin
170
configure: include path: NONE/include
171
seal plugin : enabled
167
seal plugin : disabled because the following libraries are missing : seal.
172 168
zustre plugin : enabled
173 169
tiny plugin : enabled
174 170
salsa plugin : disabled because the following libraries are missing : salsa.
......
183 179
checking for gcc option to accept ISO C89... none needed
184 180
checking for __gmpz_init in -lgmp... yes
185 181
checking for mpfr_add in -lmpfr... yes
186
configure: ../lustrec-tests/regression_tests
187
checking for ../lustrec-tests/regression_tests/CMakeLists.txt... yes
188 182
configure: creating ./config.status
189 183
config.status: creating Makefile
190 184
config.status: creating src/dune
185
config.status: creating plugins/zustre/dune
191 186
config.status: creating src/pluginList.ml
192 187
config.status: creating src/verifierList.ml
193 188
config.status: creating lib/version.ml
194 189
config.status: creating share/FindLustre.cmake
195
configure: ****** Regression Tests  ******
196
configure: tests path: ../lustrec-tests/regression_tests
197
configure: ******** Configuration ********
198
configure: Execute "make; make install" now
199 190

  
200 191
$ dune build
201 192

  
......
212 203
 * `main_lustre_verifier`  for lustrev
213 204
 * `main_lustre_testgen` for lustret
214 205

  
206

  
207
To build the executable like they will be released you can use `dune build @install`.
208
The executables will be located at `_build/install/default/bin`. The main difference with a simple build is that there will be no source code in the @install build, and the binaries will be put in the bin folder with there public names (lustrec, lustrev, lustret for instance), not the name of their Ocaml modules.
209

  
210
## How to install ? 
211

  
212
As a developper you have two ways of installed lustrec binaries so that there are available systemwide.
213

  
214
### With opam 
215

  
216
``` 
217
$ opam pin --kind=local . # add lustrec packages to opam
218
$ opam depext lustrec # install the required system dependencies
219
$ opam install lustrec # install Lustrec
220
```
221

  
222
### Without opam (with dune)
223

  
224
Simply run :
225
```
226
dune build @install
227
dune install
228
```
229

  
230
Beware that dune is just the build system, so dependencies will not be resolved and installed.
231

  
215 232
## Dockerfile.ubuntu 
216 233

  
217 234
This Dockerfile install the lustrec, lustrev and lustret tools in an Ubuntu 20.04 container.
......
225 242
$ dune-deps | tred | dot -Tpng > deps.png
226 243
```
227 244

  
245
## Release process
246
Example for "v0.1" : 
247

  
248
opam install dune-release
249

  
250
```
251
git tag -a 0.1
252
git push origin 0.1
253
``` 
254

  
255

  
256

  
257

  
228 258
# People
229 259
  * Pierre-Loic Garoche (ONERA)
230 260
  * Xavier Thirioux (IRIT)

Also available in: Unified diff