You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not completely clear on how we want to build PETSc in the long run. (On Mac and Windows, we will probably need to ship dylib and dll binaries, respectively. On Ubuntu etc, we may want to use prepackaged PETSc binaries via bindeps.) But in the short run, where we are building from source, it would be more Julian to:
Directly run the necessary download and make commands etc. from build.jl without using any shell script.
Output a deps/deps.jl file containing constants const libpetsc_float64 = "...." etc. defining the paths of the library files (sans .so extension)
In particular, we shouldn't rely on the user (or Julia) setting any kind of PETSC_DIR environment variables if possible. Not only are those unfriendly to subprocesses, but they also don't seem like they will work for linking multiple Petsc versions simultaneously (#6).
The text was updated successfully, but these errors were encountered:
I'm not completely clear on how we want to build PETSc in the long run. (On Mac and Windows, we will probably need to ship
dylib
anddll
binaries, respectively. On Ubuntu etc, we may want to use prepackaged PETSc binaries via bindeps.) But in the short run, where we are building from source, it would be more Julian to:download
andmake
commands etc. frombuild.jl
without using any shell script.deps/deps.jl
file containing constantsconst libpetsc_float64 = "...."
etc. defining the paths of the library files (sans.so
extension)In particular, we shouldn't rely on the user (or Julia) setting any kind of
PETSC_DIR
environment variables if possible. Not only are those unfriendly to subprocesses, but they also don't seem like they will work for linking multiple Petsc versions simultaneously (#6).The text was updated successfully, but these errors were encountered: