Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Stephen G Tuggy
@stephengtuggy
OK, cool
Benjamen Meyer
@BenjamenMeyer
good news - https://github.com/vegastrike/Vega-Strike-Engine-Source/releases/tag/v0.7.0-beta7 - has all the various packages...50 of them :)
Stephen G Tuggy
@stephengtuggy
Yes, I just saw that :-)
Benjamen Meyer
@BenjamenMeyer
we probably need to cut that down to what each platform generates some how
we don't need the various compressed files from every build, just one of them
Stephen G Tuggy
@stephengtuggy
So we finally have a complete Vega Strike 0.7.x beta release, built using GitHub Actions CD! :tada:
Yes. In fact, I think we only need the .deb's and the .rpm's.
Benjamen Meyer
@BenjamenMeyer
:+1:
well; the various other archives are good to have too for folks, but we only need one copy of them.
we can fix that as we go
Stephen G Tuggy
@stephengtuggy
yep
Benjamen Meyer
@BenjamenMeyer
@stephengtuggy can you give vegastrike/Assets-Production#46 a quick review again?
Stephen G Tuggy
@stephengtuggy
sure. Doing that right now
Benjamen Meyer
@BenjamenMeyer
cool; thanks!
Stephen G Tuggy
@stephengtuggy
no problem
well, time for me to hit the hay
Good night, all
Benjamen Meyer
@BenjamenMeyer
I think we need to figure out and address the issue in follow-on PRs once we figure out the APIs a bit; that way we can get our releases out. We can always complain to GH about https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswithargs not supporting lists of strings and point to the stuff as why they need to.
Roy Falk
@royfalk

My system is back up, now with Ubuntu 20.10 (Groovy). However, I have an issue with boost. 1.67 was replaced by 1.71 and it's complaining:

CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:117 (find_package):
Found package configuration file:
/usr/lib/x86_64-linux-gnu/cmake/boost_python-1.71.0/boost_python-config.cmake

Still working on figuring it out. I'm not the only one but there doesn't seem to be a solution. I'd rather not reinstall 20.04 just to solve this, so we'll see.

Benjamen Meyer
@BenjamenMeyer
@royfalk is that on a clean build environment (make clean)?
Roy Falk
@royfalk
The OS, yes. The source code folders were copied from the old partition.
Benjamen Meyer
@BenjamenMeyer
you may want to clean the source code
it might be trying to matching old build objects up; cleaning out the build objects and cmake caches should do the trick
Roy Falk
@royfalk
Clean how? It's failing at cmake.
From what I could find, it's an issue with the newer boosts and we're not the only ones.
Benjamen Meyer
@BenjamenMeyer
$ mkdir build
$ cd build
$ cmake ../engine
$ cd ..
$ rm -Rf build
CMake caches a lot of stuff; just saying it's worth eliminating as a possible issue. If it still persists after that we'll have to figure it out in more depth.
Roy Falk
@royfalk
I just did. No joy.
Benjamen Meyer
@BenjamenMeyer
thanks for validating
Roy Falk
@royfalk
Made it work by requiring python3. I guess we'll see during merge how it really works on other systems.
Benjamen Meyer
@BenjamenMeyer
ahh...yeah, that's probably required for 20.10 since they probably dropped Py2 support as it would be completely EOL before 21.04 was released.
@royfalk can you add some content to the Install page about that?
Roy Falk
@royfalk
I will, just as soon as I can confirm it works.
G'night.
Stephen G Tuggy
@stephengtuggy
yeah, Boost 1.71 and later do not support Python 2.
I actually ran into that issue on Ubuntu 20.04 as well. I worked around it by choosing the older 1.67 Boost libraries, instead of the default, newer Boost libraries available for 20.04.
Fedora 32 and 33 don't support py2 either. There are probably other distros like that as well.
The good thing is that Python 3 works, as far as I've tested it.
I'm thinking that around the 0.9.x timeframe, we can probably revise the bootstrap script for Ubuntu 20.04 to use the newer version of Boost again. Then we just won't worry about py2 after that.
I'll be happy when we get to that point
Benjamen Meyer
@BenjamenMeyer
:+1:
Stephen G Tuggy
@stephengtuggy
Hopefully that will be some help for someone (maybe me) trying to get Vega Strike building under Windows.
Loki1950
@Loki1950
:+1:
Benjamen Meyer
@BenjamenMeyer
Okay...learning about man pages and nroff/troff formatting...yeah... any how.. updated the man page for VS - vegastrike/Vega-Strike-Engine-Source#412
@Loki1950 could you please take a look; suggestions around the Authors section would be appreciated for any authors we should call out.
Benjamen Meyer
@BenjamenMeyer
@ministerofinformation how update to date is https://2.7kelvin.com/?
Loki1950
@Loki1950
Just reviewed your change to #412 :+1:
Benjamen Meyer
@BenjamenMeyer
thanks; vegastrike/Vega-Strike-Engine-Source#413 for pushing the changes to master - cherry-picked the same commits; didn't require any other changes :) so should be pretty straight forward.
(delta of the two files is basically just the version text)
Benjamen Meyer
@BenjamenMeyer