Home
last modified time | relevance | path

Searched refs:build (Results 1 – 25 of 74) sorted by relevance

123

/petsc/src/binding/petsc4py/
H A Dmakefile3 default: build
14 .PHONY: config build test
17 build: target
18 ${PYTHON} setup.py build ${opt}
36 -${RM} -r build _configtest.* *.py[co]
46 install: build
116 SPHINXBUILD = sphinx-build
121 mkdir -p build/doctrees docs/html
122 ${SPHINXBUILD} -a -b html -d build/doctrees ${SPHINXOPTS} \
126 mkdir -p build/doctrees build/latex
[all …]
H A Dpyproject.toml1 [build-system]
7 build-backend = "setuptools.build_meta"
H A Dsetup.cfg5 [build]
H A DCHANGES.rst37 - Update Cython build, require ``Cython >= 3.0.0``.
73 - Fix build issues after changes in recent PETSc patch releases.
75 - Update Cython build, require ``Cython >= 0.24``.
251 - Workaround build failures when PETSc is built with *mpiuni*.
276 - Added a quick fix to solve build issues. The macro __SDIR__ is no
H A D.gitignore1 build
/petsc/share/petsc/
H A DCMakeLists.txt5 # Usage: To build ex1 from ex1.c
6 # rm -fr build
7 # cmake -B build
8 # cmake --build build
9 # ./build/ex1
38 # tells CMake to build the application ex1 from the source file ex1.c
/petsc/src/binding/petsc4py/demo/legacy/wrap-f2py/
H A Dmakefile15 .PHONY:build
16 build: ${MODULE}.so target
19 run: build
28 ${RM} -r build ${MODULE}module.c
/petsc/src/binding/petsc4py/demo/legacy/wrap-cython/
H A Dmakefile15 .PHONY:build
16 build: ${MODULE}.so target
19 run: build
25 ${RM} -r build ${MODULE}.c
/petsc/src/binding/petsc4py/demo/legacy/wrap-swig/
H A Dmakefile15 .PHONY:build
16 build: ${MODULE}.py _${MODULE}.so target
19 run: build
25 ${RM} -r build ${MODULE}_wrap.c
/petsc/src/snes/tutorials/
H A Dbuild.zig5 pub fn build(b: *std.build.Builder) void {
6 // Standard target options allows the person running `zig build` to choose
7 // what target to build for. Here we do not override the defaults, which
12 // Standard release options allow the person running `zig build` to select
/petsc/
H A Dpyproject.toml1 [build-system]
6 build-backend = "setuptools.build_meta"
/petsc/src/binding/petsc4py/test/
H A Druntests.py123 from setuptools.command.build import build
125 from distutils.command.build import build
126 cmd_obj = build(Distribution())
/petsc/lib/petsc/conf/
H A Dvariables3 # This turns off any environmental variables for flags to not be used during the build process.
46 # The makefile can then use the variable values for their own rules to build executables
64 # The following variables are used by PETSc build targets.
107 # Some variables used to build shared libraries
/petsc/src/binding/petsc4py/docs/source/
H A DMakefile7 SPHINXBUILD ?= sphinx-build
H A Dinstall.rst16 First `build PETSc <petsc:doc_install>`. Next :file:`cd` to the top of the
28 your build host, then before invoking :program:`pip`, set the
/petsc/lib/petsc/bin/maint/
H A Dxclude20 petsc-dist/src/binding/petsc4py/build
42 petsc-dist/arch-build
51 petsc-dist/build.log
52 petsc-dist/build.log.bkp
/petsc/doc/
H A D.gitignore4 # Populated from the classic docs build
H A Dmakefile6 SPHINXBUILD ?= sphinx-build
/petsc/doc/install/
H A Dinstall_tutorial.md8 are installed, {ref}`download <doc_download>` PETSc and build with:
23 Don't need Fortran? Use `--with-fortran-bindings=0` to reduce the build times. If you
26 `--with-fc=0` for even faster build times.
31 3. Refer to {ref}`configuration faq <doc_config_faq>` (e.g. build PETSc without a
39 Configure stage complete. Now build PETSc libraries with:
252 Configure stage complete. Now build PETSc libraries with (gnumake build):
261 After successfully configuring, build the binaries from source using the `make`
H A Dwindows.md54 2. To build with Cygwin installed BLAS, LAPACK, and Open MPI (from default locations), do (from `Cy…
60 3. Follow the Unix instructions for any additional configuration or build options.
117 …compiler wrapper script `win32fe_cl` that uses `win32fe` [^win32] and then build the libraries with
137 …rks with `--with-shared-libraries=0` only, `ifort` is recommended for default shared library build.
177 compiler versions etc. used for any given build of PETSc, so they are potentially
178 different for each build of PETSc. So if you need a project file for use with PETSc -
H A Dmultibuild.md40 - Specify variable on commandline (bash) to build an example in
55 The first time you build PETSc, you must first run `configure` which (among other
93 `--with-clean`. This will **permanently delete all build files, including installed
179 While it is automatically done for you the first time you `configure` and build PETSc,
/petsc/doc/changes/
H A D213.md9 - win32fe updates for better build support on Microsoft Windows 98 machines,
/petsc/lib/petsc/bin/
H A Dpetscmpiexec79 …ME " "${PETSC_DIR}/${PETSC_ARCH}/lib/petsc/conf/petscvariables" | grep -v build | grep -v include …
/petsc/doc/developers/
H A Dbuildsystem.md9 ## What is a build?
11 The build stage compiles source to object files, stores them
20 necessary for the build stage. This is a far more complicated task, heavily dependent on
21 the local hardware and software environment. It is also the source of nearly every build
87 configure and build system for the package is used, and special support
224 a section named for the package. The second task is to build the tree of
248 directory and a build name so that multiple independent builds can be
309 suggested interaction of a new build system with the Framework. If a
H A Ddevelopment.md6 build and development environment.

123