jam-build 0.6.0__tar.gz

jam_build-0.6.0/.github/workflows/pypi.yml

@@ -0,0 +1,87 @@
+name: Publish Python 🐍 distribution 📦 to PyPI
+
+on: push
+
+jobs:
+  build:
+    name: Build distribution 📦
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+      with:
+        persist-credentials: false
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.x"
+    - name: Install pypa/build
+      run: >-
+        python3 -m pip install build --user
+    - name: Build a binary wheel and a source tarball
+      run: python3 -m build
+    - name: Store the distribution packages
+      uses: actions/upload-artifact@v4
+      with:
+        name: python-package-distributions
+        path: dist/
+
+  publish-to-pypi:
+    name: >-
+      Publish Python 🐍 distribution 📦 to PyPI
+    if: startsWith(github.ref, 'refs/tags/')  # only publish to PyPI on tag pushes
+    needs:
+    - build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/jamp
+    permissions:
+      id-token: write  # IMPORTANT: mandatory for trusted publishing
+
+    steps:
+    - name: Download all the dists
+      uses: actions/download-artifact@v4
+      with:
+        name: python-package-distributions
+        path: dist/
+    - name: Publish distribution 📦 to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
+
+  github-release:
+    name: >-
+      Sign the Python 🐍 distribution 📦 with Sigstore
+      and upload them to GitHub Release
+    needs:
+    - publish-to-pypi
+    runs-on: ubuntu-latest
+
+    permissions:
+      contents: write  # IMPORTANT: mandatory for making GitHub Releases
+      id-token: write  # IMPORTANT: mandatory for sigstore
+
+    steps:
+    - name: Download all the dists
+      uses: actions/download-artifact@v4
+      with:
+        name: python-package-distributions
+        path: dist/
+    - name: Sign the dists with Sigstore
+      uses: sigstore/gh-action-sigstore-python@v3.0.0
+      with:
+        inputs: >-
+          ./dist/*.tar.gz
+          ./dist/*.whl
+    - name: Create GitHub Release
+      env:
+        GITHUB_TOKEN: ${{ github.token }}
+      run: >-
+        gh release create "$GITHUB_REF_NAME" --repo "$GITHUB_REPOSITORY" --notes ""
+    - name: Upload artifact signatures to GitHub Release
+      env:
+        GITHUB_TOKEN: ${{ github.token }}
+      # Upload to GitHub Release using the `gh` CLI.
+      # `dist/` contains the built packages, and the
+      # sigstore-produced signatures and certificates.
+      run: >-
+        gh release upload "$GITHUB_REF_NAME" dist/** --repo "$GITHUB_REPOSITORY"

jam_build-0.6.0/.github/workflows/python-package.yml

@@ -0,0 +1,39 @@
+# This workflow will install Python dependencies, run tests and lint with a variety of Python versions
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python
+
+name: Python package
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v3
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        python -m pip install flake8 pytest networkx
+    - name: Lint with flake8
+      run: |
+        # stop the build if there are Python syntax errors or undefined names
+        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+        # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics --ignore=E203,C901,W503 --exclude='*src/jamp/yacc.py','*src/jamp/__init__.py'
+    - name: Test with pytest
+      run: |
+        pytest

jam_build-0.6.0/.gitignore

@@ -0,0 +1,12 @@
+__pycache__
+/jamtests
+/dist
+tags
+parser.out
+
+.ninja_log
+.ninja_deps
+build.ninja
+*.o
+*.o.d
+*.cache

jam_build-0.6.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Ildus Kurbangaliev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

jam_build-0.6.0/PKG-INFO

@@ -0,0 +1,117 @@
+Metadata-Version: 2.4
+Name: jam-build
+Version: 0.6.0
+Summary: Jam Build System (based on Python)
+Project-URL: Homepage, https://github.com/ildus/jamp
+Project-URL: Issues, https://github.com/ildus/jamp/issues
+Author-email: Ildus Kurbangaliev <i.kurbangaliev@gmail.com>
+License-File: LICENSE
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Requires-Dist: networkx>=3
+Provides-Extra: tests
+Requires-Dist: pytest>=8.3.3; extra == 'tests'
+Description-Content-Type: text/markdown
+
+Jam build system on Python
+--------------------------
+
+This is a Python reimplementation of the Jam build system
+([link](https://swarm.workshop.perforce.com/projects/perforce_software-jam)).
+
+Supported platforms: Linux (Unix), OpenVMS, Windows (WIP)
+
+What is Jam
+------------
+
+Jam is a build system (similar to meson, cmake, etc.). The key difference is that its core is
+essentially an interpreter for its internal language, with all building functionality
+written in this language.
+
+The raw Jam language doesn't know how to build anything by itself, but it allows you to define rules
+and dependencies which construct the actual command sequence to build
+projects using a dependency tree.
+
+Jam includes `Jambase`, which is a collection of generic rules to build C, C++ and
+Fortran projects. It can be easily extended (or modified)
+to support other types of projects.
+
+Differences from the original Jam
+-----------------------------
+
+* Uses `ninja`, `samurai` or other `ninja`-compatible builders for
+    the actual building of executables.
+* `mkdir` is a built-in command that collects all created directories to the `dirs` target.
+* Built-in rules are case-insensitive (`Echo` and `ECHO` are the same).
+* Regular expressions are Python-based.
+* `Clean` actions are ignored in favor of `ninja -t clean`.
+
+Quick Start
+-----------
+
+Install:
+
+    # Install jamp with the system pip
+    pip3 install git+https://github.com/ildus/jamp
+
+    # Using pypy3 provides approximately twice the performance
+    # pypy3 -m pip install git+https://github.com/ildus/jamp
+
+    # Install ninja using your package manager
+    dnf install ninja
+    # or pacman -Syu ninja
+    # etc.
+
+Example project structure with a library and a main executable that uses math functions:
+
+    src
+        main.c
+    lib
+        print.c
+    include
+        common.h
+
+    Jamfile
+
+Corresponding Jamfile:
+
+    HDRS = include ;                    # common includes, affects all sources
+    Library libprint : lib/print.c ;    # on Unix this will create libprint.a
+    Main app : src/main.c ;             # executable
+    LinkLibraries app : libprint ;      # linking the executable with our library
+    LINKLIBS on app = -lm ;             # system libraries
+
+To build the executable, simply run:
+
+    jamp && ninja
+
+For more complex examples, look at the `tests` directory. When dealing with subdirectories,
+it's recommended to use the `SubDir` rule. Note that this example should work on Windows
+and Linux (because of explicit paths), but will not work on VMS.
+
+Contributing
+-----------
+
+    git clone git@github.com:ildus/jamp.git
+
+    # To run without installing
+    export PYTHONPATH=$PYTHONPATH:<current_dir>/jamp/src
+    python3 -m jamp
+
+    # Testing changes
+    pip install pytest
+    cd <jamp root folder>
+    pytest
+
+Documentation
+-------------
+
+See the `docs` directory.
+
+OpenVMS Notes
+---------------
+
+Use my `github.com/ildus/samurai` fork for compilation. It supports the additional '$^' escape
+sequence for newlines, allowing you to add full scripts to `build.ninja`.

jam_build-0.6.0/README.md

@@ -0,0 +1,100 @@
+Jam build system on Python
+--------------------------
+
+This is a Python reimplementation of the Jam build system
+([link](https://swarm.workshop.perforce.com/projects/perforce_software-jam)).
+
+Supported platforms: Linux (Unix), OpenVMS, Windows (WIP)
+
+What is Jam
+------------
+
+Jam is a build system (similar to meson, cmake, etc.). The key difference is that its core is
+essentially an interpreter for its internal language, with all building functionality
+written in this language.
+
+The raw Jam language doesn't know how to build anything by itself, but it allows you to define rules
+and dependencies which construct the actual command sequence to build
+projects using a dependency tree.
+
+Jam includes `Jambase`, which is a collection of generic rules to build C, C++ and
+Fortran projects. It can be easily extended (or modified)
+to support other types of projects.
+
+Differences from the original Jam
+-----------------------------
+
+* Uses `ninja`, `samurai` or other `ninja`-compatible builders for
+    the actual building of executables.
+* `mkdir` is a built-in command that collects all created directories to the `dirs` target.
+* Built-in rules are case-insensitive (`Echo` and `ECHO` are the same).
+* Regular expressions are Python-based.
+* `Clean` actions are ignored in favor of `ninja -t clean`.
+
+Quick Start
+-----------
+
+Install:
+
+    # Install jamp with the system pip
+    pip3 install git+https://github.com/ildus/jamp
+
+    # Using pypy3 provides approximately twice the performance
+    # pypy3 -m pip install git+https://github.com/ildus/jamp
+
+    # Install ninja using your package manager
+    dnf install ninja
+    # or pacman -Syu ninja
+    # etc.
+
+Example project structure with a library and a main executable that uses math functions:
+
+    src
+        main.c
+    lib
+        print.c
+    include
+        common.h
+
+    Jamfile
+
+Corresponding Jamfile:
+
+    HDRS = include ;                    # common includes, affects all sources
+    Library libprint : lib/print.c ;    # on Unix this will create libprint.a
+    Main app : src/main.c ;             # executable
+    LinkLibraries app : libprint ;      # linking the executable with our library
+    LINKLIBS on app = -lm ;             # system libraries
+
+To build the executable, simply run:
+
+    jamp && ninja
+
+For more complex examples, look at the `tests` directory. When dealing with subdirectories,
+it's recommended to use the `SubDir` rule. Note that this example should work on Windows
+and Linux (because of explicit paths), but will not work on VMS.
+
+Contributing
+-----------
+
+    git clone git@github.com:ildus/jamp.git
+
+    # To run without installing
+    export PYTHONPATH=$PYTHONPATH:<current_dir>/jamp/src
+    python3 -m jamp
+
+    # Testing changes
+    pip install pytest
+    cd <jamp root folder>
+    pytest
+
+Documentation
+-------------
+
+See the `docs` directory.
+
+OpenVMS Notes
+---------------
+
+Use my `github.com/ildus/samurai` fork for compilation. It supports the additional '$^' escape
+sequence for newlines, allowing you to add full scripts to `build.ninja`.

jam_build-0.6.0/conftest.py

@@ -0,0 +1,23 @@
+import pytest
+
+
+def pytest_configure(config):
+    import sys
+
+    sys._called_from_test = True
+
+
+def pytest_unconfigure(config):
+    import sys
+
+    if hasattr(sys, '_called_from_test'):
+        delattr(sys, '_called_from_test')
+
+
+@pytest.fixture(autouse=True)
+def run_around_tests():
+    from jamp.jam_builtins import Builtins
+
+    Builtins.clear_output()
+
+    yield