I'm not sure RE the include thing. I've just always had people yell at me that the includes need to be lowercase in Linux. Never bothered to figure out why...perhaps now is the time. Regardless, the change has already been made in my GitHub repo [thanks to Tjoppen on #nesicide] and apparently builds and runs [albeit in its current 'not yet done' form] on Linux and OSX.
The CString thing took me for a wild ride, too. I was scratching my head trying to figure out how to force conversion for variadics when I stumbled on the description that I paraphrased here.
So jsr is right in that as long as the case in the #include always matches the case in the filesystem's file name, everything should be good. Is that right? If so I'll reject the commit changing the casing, keep calm, and carry on. =]
I created a burn-down list toward completion of this project. It's here. Content as of today:
FamiTracker Qt BURN-DOWN LIST:
1. Implement following APIs for OSX compatibility:
FreeLibrary
GetClassName
GetCursorPos
GetFileAttributes
GetKeyNameText
GetProcAddress
GetWindowLong
LoadLibrary
RegisterClipboardFormat
SetCursor
(most of these are for supporting custom file exporters)
2. Finish implementing configuration dialogs.
a. Flesh out implementations of CPropertyPage, CPropertySheet.
3. Finish implementation of CMenu.
a. Finish support for sub-menus.
b. Implement hooks to UI for triggers and updates.
4. Finish implementation of accelerator keys.
a. Implement hooks to UI for triggers.
5. Implement triggers for status bar updates.
6. Finish implementation of custom controls [instrument list!]
7. MIDI
a. Find out how to do it OSX-ish or Linux-ish.
b. Consider leaving MIDI a "Windows only feature" for now.
8. FontDrawer.cpp? DialogReBar.cpp? Exception.cpp?
a. Might not need these or at least not entirely. Figure this out.
9. Test, test, test...
10. Port 0.4.2 functionality.
If there's anyone out there that can help with a cross-platform MIDI implementation [I haven't even googled for one yet], I'd appreciate some pointers. I am purposely leaving MIDI for last but I realize that it's probably a very popular feature of the tracker, so I'm hoping to make it portable. Several of the listed items are close to being done.
It seems like your GitHub link is broken. As for the packaging & delivery...
cpow wrote:
hatsize7: I run Ubuntu 12.04 in VirtualBox so that will be my Linux build test platform. Unfortunately I completely lack Linux packaging skills...but we'll figure something out.
hatsize7 wrote:
Hi cpow, source code is fine...I'm fine with compiling my own binaries. Thanks again.
I'm on a Windows 8 host with Windows XP & Lubuntu guests in VMware; as much as I'm also happy with compiling my own copy on Linux, here's some info I've dug up for you on deb packaging, to appeal to those novice Linux users who just want to get something working:
As for Windows, how would you intend to deliver pre-compiled binaries? Because you could always follow the same approach to deliver pre-compiled Linux binaries (just package it in an archive of some kind. the same way JSR delivers FamiTracker).
But concerning MIDI, it's honestly not all that popular (at least from the looks of it).
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
It seems like your GitHub link is broken. As for the packaging & delivery...
Strange. It wasn't working for a bit but now seems to be again. Maybe GitHub was having problems this afternoon.
TechEmporium wrote:
I'm on a Windows 8 host with Windows XP & Lubuntu guests in VMware; as much as I'm also happy with compiling my own copy on Linux, here's some info I've dug up for you on deb packaging, to appeal to those novice Linux users who just want to get something working:
...links...
Thanks for the links. I'll check them out.
TechEmporium wrote:
As for Windows, how would you intend to deliver pre-compiled binaries? Because you could always follow the same approach to deliver pre-compiled Linux binaries (just package it in an archive of some kind. the same way JSR delivers FamiTracker).
I've always just put a Windows installer binary [.msi] up on my webpage for my other project--NESICIDE. I'd thought about doing the same for Qt FamiTracker. I do need to have some kind of "older versions" archive, though. I also have binary-only debian packages that I managed to coddle together for NESICIDE there...but I'm told they're "not quite right". Maybe the Qt FamiTracker Win/Lin/Mac binaries could even be placed on FamiTracker.com/downloads.php alongside the originals? That'd lead to less confusion but JSR would obviously have to agree to it. =]
Oh that brings up another point...rather than release this thing to the wild and have oodles of people become disappointed because it doesn't quite measure up to the original, I'm starting to try to think of a way it could be crowd-beta'd. When it does become ready enough to put out there's likely to be some things that I've just plain overlooked because I'm not a tracker. Maybe I could just leave that to the "issues" page on GitHub and let people vent that way.
TechEmporium wrote:
But concerning MIDI, it's honestly not all that popular (at least from the looks of it).
Really? I'd always just pictured you guys as genius music makers sitting behind racks of Korg keyboards with FamiTracker on a PC screen nearby, gleefully recording each note you played. =] I'm happy leaving MIDI in Windows-only state [or "not included" in the Qt version] for now if that's not the case.
Svetlana: I'll remove it if you want but honestly it's a great tune! Perhaps I should ask for permission before putting up videos of others' work. Sorry!
Svetlana: I'll remove it if you want but honestly it's a great tune! Perhaps I should ask for permission before putting up videos of others' work. Sorry!
it's ok!! it's just that it's one of the earliest things i've made in famitracker and i don't remember even putting it online anywhere
i have more stuff in here if you want to use it feel free!
also: does porting fami to qt mean it'll be more portable to other platforms??
EDIT: nevermind i'm an idiot, i didn't fully read through anything in the thread
Maybe the Qt FamiTracker Win/Lin/Mac binaries could even be placed on FamiTracker.com/downloads.php alongside the originals? That'd lead to less confusion but JSR would obviously have to agree to it. =]
Sure that's alright with me!
cpow wrote:
8. FontDrawer.cpp? DialogReBar.cpp? Exception.cpp?
a. Might not need these or at least not entirely. Figure this out.
FontDrawer.cpp is currently unused and can safely be removed. DialogReBar.cpp is used to place dialog controls in the toolbar (used for octave and row highlight). Exception.cpp is used to generate crash memory dumps for post-mortem debugging, that can be removed for portability reasons.
TechEmporium wrote:
But concerning MIDI, it's honestly not all that popular (at least from the looks of it).
I wouldn't say that actually, MIDI was one of the earliest features I added. But then it's not essential for tracking.
) 
feel free!