Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / liballeg/allegro_winpkg issues and pull requests
#15 - Small opusfile version mistake in 1.14.0 release asset
Issue -
State: closed - Opened by geecab 11 months ago
- 1 comment
#14 - allegro build scripts for visual studio 2022
Pull Request -
State: closed - Opened by WernherVonData over 2 years ago
- 1 comment
#13 - Allegro build scripts for VS 2022
Issue -
State: closed - Opened by WernherVonData over 2 years ago
- 5 comments
#12 - Building statically linked library - Missing Imports
Issue -
State: closed - Opened by pmprog about 3 years ago
- 2 comments
#11 - Added VS2022 build dependencies batch files
Pull Request -
State: closed - Opened by sub-c about 3 years ago
- 2 comments
#10 - Building Allegro using VS2019
Issue -
State: closed - Opened by pmprog almost 4 years ago
- 7 comments
#9 - Clang target ?
Issue -
State: closed - Opened by jacmoe almost 4 years ago
- 3 comments
#8 - Include Allegro's source, so that pdb files have something they can go into easily
Issue -
State: open - Opened by SiegeLord about 7 years ago
#7 - Add nuget stuff for MSVC 2017
Pull Request -
State: closed - Opened by SiegeLord almost 8 years ago
#6 - Package libopus.
Issue -
State: closed - Opened by SiegeLord over 8 years ago
- 1 comment
#5 - Consider not including symbols in the non-debug binaries for MSYS
Issue -
State: open - Opened by SiegeLord almost 9 years ago
#4 - PDB files for Nuget
Issue -
State: closed - Opened by SiegeLord almost 9 years ago
#3 - Nuget package 2
Pull Request -
State: closed - Opened by ghost about 9 years ago
- 7 comments
#2 - First version of nuget package scripts for evaluation.
Pull Request -
State: closed - Opened by ghost over 9 years ago
- 6 comments
#1 - Small improvements to scripts
Pull Request -
State: closed - Opened by ghost over 9 years ago
- 1 comment