-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide .deb binary packages for the toolkit #20
Comments
dciabrin
added a commit
to dciabrin/ngdevkit-toolchain
that referenced
this issue
Jun 21, 2019
Split the generation of the ngdevkit toolchain into a dedicated git repository. This new repository should eventually be consumed as a git submodule by ngdevkit. Ref dciabrin/ngdevkit#20.
dciabrin
added a commit
to dciabrin/ngdevkit-toolchain
that referenced
this issue
Jun 21, 2019
Split the generation of the ngdevkit toolchain into a dedicated git repository. This new repository should eventually be consumed as a git submodule by ngdevkit. Ref dciabrin/ngdevkit#20.
dciabrin
added a commit
to dciabrin/ngdevkit-toolchain
that referenced
this issue
Jun 21, 2019
Split the generation of the ngdevkit toolchain into a dedicated git repository. This new repository should eventually be consumed as a git submodule by ngdevkit. Ref dciabrin/ngdevkit#20.
dciabrin
added a commit
to dciabrin/ngdevkit-toolchain
that referenced
this issue
Jun 21, 2019
Split the generation of the ngdevkit toolchain into a dedicated git repository. This new repository should eventually be consumed as a git submodule by ngdevkit. Ref dciabrin/ngdevkit#20.
dciabrin
added a commit
to dciabrin/ngdevkit-toolchain
that referenced
this issue
Jun 21, 2019
dciabrin
added a commit
to dciabrin/ngdevkit-examples
that referenced
this issue
Sep 7, 2019
Move ngdevkit's examples into a dedicated git repository. This new repository is meant to be consumed directly my ngdevkit, or indirectly for CI purpose. Ref dciabrin/ngdevkit#20.
dciabrin
added a commit
that referenced
this issue
Sep 14, 2019
This repository is the base devkit that includes all other modules (toolchain, emulator, examples...). It can be configured to build the entire toolkit or just to be built separately for packaging purpose. Ref #20.
dciabrin
added a commit
that referenced
this issue
Dec 1, 2019
* Split ngdevkit into separate build modules This repository is the base devkit that includes all other modules (toolchain, emulator, examples...). It can be configured to build the entire toolkit or just to be built separately for packaging purpose. Ref #20. * Fix full build * Hide more generated files * Stop depending on automake, probe python and install differently * Fix ngdevkit pkgconfig version * Move configuration of qcrt-glsl to ngdevkit-examples * Support configure and build with MinGW * Fix unconditional MinGW gngeo install target * Move gngeo config generation from ngdevkit to ngdevkit-examples * mingw: export gngeo path with devkit path, so that eval works * Configure ngdevkit-gngeo to look for config file ngdevkit-gngeorc * Fix installation to be compatible with macOS and BSD install * Fix debug feltover in distclean entry * Update README after repository split * Add optional GLEW dependency in README for GLSL shaders in GnGeo * Make zoom-rom.py py3-compatible * Make tools depend on python3 * Install pkgconfig file in standard /usr/share subdirectory * Clean autoconf-generated files on distclean * Ensure destination dir exist before installing runtime files * Rename ngdevkit's crt0 to avoid packaging name conflict with gcc * Install C include in the cross-compiler include path * Fix tools for python3 compatibility * Selectively disable downloading of ngdevkit-examples * Remove MinGW-specific makefile, no longer useful * Update README to reference deb packages for Ubuntu/Debian
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ngdevkit currently bundles several subcomponents that together form a devkit:
Grouping these component together is not ideal because any time a new commit is merged in one in the repository, users need to recompile the entire toolkit to ensure they use it.
It would be nice to somehow automatically publish new packages when new commit occurs.
Ideally, every subcomponent should be packaged independently, so that one change in a subcomponent does not force users to download all the binaries.
This issue tracks the refactoring steps needed to provide .deb packages for each subcomponent of the toolkit.
The text was updated successfully, but these errors were encountered: