x-tec2017
commented
4 years ago Ryan,What is this all about? LarrySent from my T-Mobile 4G LTE Device -------- Original message --------From: xenolithcluster notifications@github.com Date: 8/1/20 5:56 PM (GMT-05:00) To: Pinacolada64/ImageBBS ImageBBS@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [Pinacolada64/ImageBBS] Terrible makefiles (#58) I love this BBS software, but wow this source tree is terrible. This isn't meant as a personal attack or anything but as someone who likes to be able to just build my programs without having to fuck around in the makefiles too much, or fix errors, this is awful I'm focused on the V2 tree here, (in master, NOT the v2 Branch) First off you're relying on using wine on specific beta versions of freeware non-open source software (C64list), i recommend not doing that as a future update could fuck shit up, and since we don't have the source, it can't be unfucked. Not to mention they're distributing the binaries through links of facebook, ew. Second of all, building. I believe the makefile is incomplete, but here are some pointers. I understand Makefile IS a major pain in the arse to work with, but it makes things easier for the user. First off, there seem to be minor syntax errors in: v2\asm\swap3.asm on line 112, thee's a missing space, it should be "ldy #0" v2\asm\irqhn.asm on line 315 (I think just changing the #',' to #$2c shoould be equivelent? Now, by using the latest version (4.03 at the moment) of C64 list it seems to build okayish, but not all the way into d64s or a d81. I get ecs.bin garbage-collect.bin swap1.bin swap3.bin editor.bin struct.bin swap2.bin wedge.bin I haven't gone any further yet, but i'm hoping this is at least what i need to put into a disk with different names to get something to work? Sorry if i sound super critical, i get this is tough work, but i do think it's important to at least get the project building or at least offer the latest working binaries in the Releases section so people can actually access the software easier without hunting down binaries elsewhere
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
jcobol
I love this BBS software, but wow this source tree is terrible. This isn't meant as a personal attack or anything but as someone who likes to be able to just build my programs without having to fuck around in the makefiles too much, or fix errors, this is awful
I'm focused on the V2 tree here, (in master, NOT the v2 Branch)
First off you're relying on using wine on specific beta versions of freeware non-open source software (C64list), i recommend not doing that as a future update could fuck shit up, and since we don't have the source, it can't be unfucked. Not to mention they're distributing the binaries through links of facebook, ew.
Second of all, building. I believe the makefile is incomplete, but here are some pointers. I understand Makefile IS a major pain in the arse to work with, but it makes things easier for the user.
First off, there seem to be minor syntax errors in: v2\asm\swap3.asm on line 112, thee's a missing space, it should be "ldy #0" v2\asm\irqhn.asm on line 315 (I think just changing the #',' to #$2c shoould be equivelent?
Now, by using the latest version (4.03 at the moment) of C64 list it seems to build okayish, but not all the way into d64s or a d81.
I get ecs.bin garbage-collect.bin swap1.bin swap3.bin editor.bin struct.bin swap2.bin wedge.bin
I haven't gone any further yet, but i'm hoping this is at least what i need to put into a disk with different names to get something to work?
Sorry if i sound super critical, i get this is tough work, but i do think it's important to at least get the project building or at least offer the latest working binaries in the Releases section so people can actually access the software easier without hunting down binaries elsewhere