When we finish getting multiarch deployed in Debian/Ubuntu, you should be able to continue to just release i386 builds and have it Just Work on x86-64 machines.

Releasing debs marked with the _any architecture with ELFs inside is kinda not cricket.

I have a laptop with a Core2Duo running amd64 debian sid, and could set it up to do builds if that's all that's needed.

Any help re 64 bit would be madly appreciated. I realize I'm not being kosher -- lintian even told me so. But that's even more so why I said "shot in the dark".

I hadn't tried to put together source packages...is that what I need to do? Or do you mean you could build from source on that machine and then put together proper x64 binary packages? PM me if you truly can help! [I mean, have the time and interest to, and all that.]

I'm on Ubuntu x64 right now, am at school, am all the time now basically, until I boot Win7 for a few weeks just to. If I can help tell me, but I'm not very good at putting linux stuff together honestly, although I know how to press CTRL+F9 in code::blocks, if that helps.

ETA: Tried the any.deb, it says Wrong architecture 'any'. But if you make any "amd64" it should work, or at least let me attempt to install it. Although, I still think it does need a special compile too, but eh, worth a shot too maybe? But shouldn't your compiler have a 64-bit option even if 32-bit? Hmm...

cl65: Don't know what to do with `obj/nes/game.d'...it looks like --create-deps is passed to ca65, which is an unknown option.

The earliest version of the compiler that will work is 2.13.9 snapshot, available here.

Nice! I compiled from SVN and all compiles nicely now.
Some problems I noticed: (only one critical)

I compiled Alter Ego, set size of the font in Project Properties, closed and relaunched Nesicide. Now, whenever I try to open Project Properties, it crashes with a segfault. Now the same thing happens even with a fresh copy of Alter Ego (or anything else). I would post my config file; I just don't know where it is

C headers didn't have syntax highlighting.

There's a noticeable hang up when closing a project; I believe it's trying to fetch nesicide's welcome page.

I compiled Alter Ego, set size of the font in Project Properties, closed and relaunched Nesicide. Now, whenever I try to open Project Properties, it crashes with a segfault. Now the same thing happens even with a fresh copy of Alter Ego (or anything else). I would post my config file; I just don't know where it is

NESICIDE.conf file is in ~/.config/CSPSoftware. I'll try here to reproduce the above while waiting.

There's a noticeable hang up when closing a project; I believe it's trying to fetch nesicide's welcome page.

Yes I get that here also. It isn't related to the welcome page -- at least here on my system it happens even when that page isn't set to show at start-up. A related bug that I'm looking into has crept in because of recent changes to support multiple targets [NES and C=64 at present]. When a project is opened or closed there's a flurry of activity creating or destroying appropriate UI elements for the target being emulated in the project being opened or closed. However, the delay you mention has been there on project closing even before this new change.

NESICIDE.conf file is in ~/.config/CSPSoftware. I'll try here to reproduce the above while waiting.

I was able to reproduce the Project Properties problem easily here so have fixed it. I'm still weeding through problems introduced in the IDE framework from the recent addition of support for C=64 target debugging [via remote monitor port connection to VICE emulator]. This was one of those. I've committed to my local Git but won't be able to push to the repositories on gitorious until later this evening. Meanwhile I'll go and look at the rest.

Thanks a lot for the fixes!
About the slow-down, maybe you can use gcov to narrow down the problematic line.

I'm using Arch Linux, so I can rather prepare PKGBUILDs (for cc65-svn c64-emulator-lib-git nes-emulator-lib-git nesicide-git nesicide-emulator-git) and post them here (I can't promise they'll get into AUR though). Would it be okay?

I'm using Arch Linux, so I can rather prepare PKGBUILDs (for cc65-svn c64-emulator-lib-git nes-emulator-lib-git nesicide-git nesicide-emulator-git) and post them here (I can't promise they'll get into AUR though). Would it be okay?

Any help is appreciated. What you've said is foreign to me, though, so I will need to consult the almighty google to educate myself. Blast Linux and all its incarnations!

I'm using Arch Linux, so I can rather prepare PKGBUILDs (for cc65-svn c64-emulator-lib-git nes-emulator-lib-git nesicide-git nesicide-emulator-git) and post them here (I can't promise they'll get into AUR though). Would it be okay?

Any help is appreciated. What you've said is foreign to me, though, so I will need to consult the almighty google to educate myself. Blast Linux and all its incarnations!

lol Let me try to save the trouble for you.
In case you are familiar with Gentoo ebuilds (I saw a it mentioned in the About Nesicide window), Arch Linux's PKGBUILD is something similar (but more primitive) to them. It's like a script that will fetch the sources from the upstream, compile and install, but just specific to Arch Linux.
They are not the part of the official repos though, it's just another mechanism for people to install packages that doesn't exists in the official repos, and also serving as a tool for building from sources.

In fact, there are already several (orphan) PKGBUILDs
nesicide-git: https://aur.archlinux.org/packages.php?ID=48433nesicide-emulator-lib-git: https://aur.archlinux.org/packages.php?ID=48434which I belive used to work with Nesicide 1. They require minimal changes, but there's a catch; the repos don't seem to be independent. I could have the packages
nesicide-c64-emulator-lib-git nesicide-emulator-lib-git nesicide-git nesicide-emulator-git
but it seems nes-emulator-lib requires nesicide sources. Which makes me consider: should I instead have single, monolithic package that will pull in everything. What do you think?

(edit: nesicide-emulator-git or nes-emulator-git?)

Last edited by torrasque on Mon May 07, 2012 1:32 pm, edited 3 times in total.

Which makes me consider: should I instead have single, monolithic package that will pull in everything. What do you think?

Yes. I am intending to merge all four repositories into one repository as soon as I can figure out how to do so in git without losing history. If I can't figure it out I might just create a new "fresh start" master repo and put everything in it as if I'm starting from scratch, at which point the four existing repos will be obsoleted. Then I'll push the big red "history eraser" button.

So, having a single monolithic package is probably a good idea. Maybe we should take this into PM.

torrasque wrote:

but there's a catch; the repos don't seem to be independent

This is true because of my hatred of repeating code fragments. Unfortunately there's some code that's required on both sides of the fence [the IDE framework or the emulator libraries].

Who is online

Users browsing this forum: No registered users and 6 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum