| 00:24.44 | macsforme | if we move modeltool to its own repo, how will autotools users build it? should we create a configure.ac file just for modeltool? |
| 00:32.11 | macsforme | that seems slightly superfluous, since modeltool has no dependencies and no configuration options... we could alternatively just write a makefile by hand |
| 00:32.45 | blast007 | we should use premake ;) |
| 00:33.43 | blast007 | you could probably just give a g++ command line to run |
| 00:34.21 | macsforme | sorry, I don't speak sarcasm |
| 00:45.34 | blast007 | g++ -I. -Wall -Wextra -Wcast-qual -Wredundant-decls -Wshadow -Wundef -pedantic -fexpensive-optimizations -g -O2 -std=c++0x -o modeltool *.cxx |
| 00:45.37 | blast007 | bam, done |
| 00:53.44 | macsforme | or, we could put that in a makefile |
| 00:54.21 | blast007 | does macOS still have g++? |
| 00:55.02 | allejo | it's in my /usr/bin/ so it's not installed via brew for me (i think) |
| 01:24.04 | *** join/#bzflag JeffM (sid48618@gateway/web/irccloud.com/x-bbsdqxirgaolrlqr) |
| 01:24.04 | *** mode/#bzflag [+v JeffM] by ChanServ |
| 01:24.24 | macsforme | clang emulates gcc when you use gcc, g++, etc. |
| 01:28.55 | blast007 | does that command work on recent macOS? |
| 01:34.33 | macsforme | yes |
| 01:34.46 | macsforme | oh, your one-liner? |
| 01:36.47 | blast007 | yeah |
| 01:36.52 | macsforme | http://pastebin.com/2MXca9pY |
| 01:37.20 | blast007 | that's not current code |
| 01:38.39 | macsforme | http://pastebin.com/f8jPsLa9 |
| 01:39.53 | blast007 | looks similar to when I ran g++ -o modeltool *.cxx, so it probably doesn't support some of those flags |
| 01:41.30 | blast007 | specifically, when I remove the -std=c++0x, I get similar errors |
| 01:45.34 | blast007 | does it do the same thing with -std=c++11 instead? |
| 01:49.54 | macsforme | no, similar error |
| 01:51.09 | macsforme | actually, it's not compiling even in Xcode anymore |
| 01:52.13 | the_map | not my fault |
| 01:52.14 | the_map | probably |
| 01:59.51 | *** join/#bzflag BZnotify (~BZnotify@192.30.252.34) |
| 01:59.51 | BZnotify | [13bzflag] 15macsforme pushed 1 new commit to 062.4: 02https://git.io/vD8Yf |
| 01:59.51 | BZnotify | 13bzflag/062.4 14e9dfe32 15Joshua Bodine: Fixed the modeltool build on macOS. |
| 01:59.51 | *** part/#bzflag BZnotify (~BZnotify@192.30.252.34) |
| 02:00.01 | macsforme | now your one-liner works too, except for the warning about -fexpensive-optimizations not being supported |
| 02:04.21 | blast007 | and that was just all copied from what our autotools did |
| 02:05.06 | blast007 | our autotools build did each source file separately and then used libtool to spit out the final binary, though |
| 02:11.13 | BulletCatcher | Writing a simple makefile by hand ought to be plenty if we move modeltool to its own branch or repo. |
| 02:11.48 | BulletCatcher | And if it turns out we need more than that I'm sure we'll do what's necessary. :-) |
| 03:06.27 | *** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net) |
| 03:09.12 | JeffM | It can loose the quake 3 support |
| 04:37.03 | blast007 | so, what would we prefer for a repository naming scheme for the various web services? i.e., the main site, resource hosting, list server, etc |
| 04:37.55 | blast007 | planning on doing the main site first so we can start writing some proper end-user documentation |
| 04:39.28 | the_map | what you do is take the default repo name that github suggests |
| 04:40.29 | blast007 | the_map: so, blank? :P |
| 04:40.40 | the_map | s/default // |
| 04:40.41 | blast007 | oh god, it actually does have suggestions |
| 04:40.53 | blast007 | "Great repository names are short and memorable. Need inspiration? How about sturdy-couscous." |
| 04:41.11 | the_map | blast007: way to try to mock my suggestion :) |
| 04:41.12 | blast007 | ooo, glowing-waffle |
| 04:41.16 | RoscoePColtrane | I like sturdy-couscous... not sure for what, but I like it |
| 04:41.29 | the_map | with honey |
| 04:41.44 | blast007 | the rewrite of BZFlag will now be called Glowing Waffle |
| 04:42.04 | blast007 | the great glowing waffle in the sky |
| 04:42.54 | blast007 | I should probably make sure our code works with PHP 7.0 |
| 04:42.55 | BulletCatcher | glowing-waffle.com is available. Register it quick! |
| 04:43.08 | blast007 | it's even available without the hyphen |
| 04:46.46 | blast007 | still working on my fancy bash scripts for building my server cluster - need to work on the iptables rules next |
| 04:49.03 | BulletCatcher | If you're going to put each web site into its own repo, then name the repo for the domain name: bzflag.org, wiki.bzflag.org, forums.bzflag.org, etc. |
| 04:49.23 | BulletCatcher | Dots are allowed in repo names. |
| 04:49.32 | the_map | glowing-waffle.bzflag.com |
| 04:50.12 | RoscoePColtrane | glowing-waffle.bzflag.com/maple-syrup |
| 04:50.24 | RoscoePColtrane | .org |
| 04:50.44 | blast007 | and of course, we need the new nomnom:// protocol |
| 04:51.09 | the_map | http: Happy To Take Pancakes |
| 04:51.32 | the_map | https is better though; we get syrup that way |
| 04:53.03 | blast007 | BulletCatcher: just the raw hostname, or should there be some prefix as well? |
| 04:53.25 | allejo | votes raw |
| 04:53.38 | the_map | eww |
| 04:54.42 | allejo | raw's my favorite photo format |
| 04:54.50 | allejo | also raw is favorite cooking of steak |
| 04:55.36 | blast007 | allejo: k, so raw-wiki.bzflag.org it is |
| 04:55.39 | blast007 | ducks |
| 04:56.11 | allejo | it's almost as if you could read my mind |
| 04:56.53 | RoscoePColtrane | I prefer my meat dead |
| 04:56.55 | the_map | I mean, that's not terribly hard |
| 04:56.58 | the_map | ducks too |
| 05:00.15 | BulletCatcher | I don't have a strong preference among bzflag.org, bzflag.org_web_site, and web_bzflag.org . |
| 05:07.25 | allejo | bzflag.org would follow conventions in other projects |
| 05:14.06 | BulletCatcher | It's concise, and a brief GitHub description like "the bzflag.org web site configuration" would provide a further clue. |
| 05:21.44 | allejo | ^ |
| 05:27.13 | BulletCatcher | Multiple services such as http, ftp, dns, etc., could be in separate branches inside the repo. |
| 05:28.22 | BulletCatcher | Or separate repos: http_bzflag.org, ftp_bzflag.org, dns_bzflag.org. |
| 05:28.23 | blast007 | to me that seems kinda messy |
| 05:29.04 | blast007 | yeah, I'd prefer separate repos for related but separate things |
| 05:29.09 | BulletCatcher | The more things you have, the messier it will be at some level. |
| 05:29.56 | blast007 | I'd probably just document the necessary webserver configuration within each web repo |
| 05:47.04 | *** join/#bzflag jnoob22 (~jnoob@c-24-8-43-250.hsd1.co.comcast.net) |
| 05:47.04 | *** join/#bzflag jnoob22 (~jnoob@unaffiliated/jnoob22) |
| 06:04.49 | BulletCatcher | And now I have experimented with Premake4 for my personal project. |
| 06:04.53 | BulletCatcher | Premake4 seems to be more flexible and have a more consistent language (because it is based on Lua) than CMake. |
| 06:04.57 | BulletCatcher | CMake has useful features like "check for a system header file" built in, while in Premake4 you would either write it yourself or download a module. |
| 06:04.58 | BulletCatcher | I give Premake4 a slight edge over CMake because we would need its flexibility for BZFlag. |
| 13:45.04 | *** join/#bzflag nadir (uid134094@gateway/web/irccloud.com/x-bhhmijzxwlyncjvf) |
| 21:25.57 | *** join/#bzflag Zehra (~Zehra@unaffiliated/zehra) |
| 22:16.10 | *** join/#bzflag disco- (~disco@unaffiliated/disco-) |