Again, I need more context. It's very hard to help if I don't know what you're running (particularly what options you're passing to cmake and what you expect to happen).

In the binary zip file I downloaded, in the bin folder, the exe I'm using is called, "cmake-gui.exe". This whole thing is confusing me.


Edit: I just found the installer link.

*DOUBLE POST*
I wish I didn't have to compile this myself. It is so difficult. Grr...

Fine, here you go.
http://jenkins.taricorp.net/job/fx-cg-cl/
You'll want the mingw32 build for Code::Blocks on windows. The library is compiled for 64-bit targets only, because important features (direct input mappings) won't work on 32-bit Windows without some fiddling.
That is to say, you'll need a 64-bit operating system and GCC to use that precompiled library.

What do I click(Sorry for all this trouble )?

I would think that if Tari said "mingw32 build", that when the options are amd64-mingw32msvc-gcc and Native, the correct choice would be amd64-mingw32msvc-gcc.

Yes but that doesn't give me a download when I click it.

Last build -> Build Artifacts -> (all files in zip)

What do I do with the libfx-cg-cl.a file and the include folder(Also, you can delete all of these posts if you need to after I'm finally done with this)?

Well, there wasn't any info that I saw on starting fx-cg-ui, so I tried and failed to get it running:
Code:

Currently using the latest fx-cg-ui from bitbucket and running python 2.7.3.

<edit>

Ah, fixed. To run fx-cg-ui, run:
Code:


Which brings me to my next issue, what is the parameter to the script? No matter what I give it, I get this
Code:

Ah, you hit one of the platform abstractions that I haven't gotten to handling in the UI yet. You can drop the "tagname='FXCGCL'" portion from line 13 there and it should work properly.

The parameter to pass to the script should be the name of a file to back the IPC interface. For now you should just be able to touch a file (I don't think size matters..) and pass its name in. You should pass the same file name to your program that uses [CL].
On Windows, you just need to pass a string that doesn't contain backslashes (no file required), and the same string to the [CL] (since shared memory isn't backed by files on Windows).

It's on my list to make the UI handle creating an IPC file when necessary and make it easy to launch a [CL] program with the correct parameters, at some point.

I'm not entirely sure everything will work correctly on python 2.x, but it appears to be okay up the problem you hit. I was doing all my development on 3.x, but we'll see how that goes for you.

Here goes more issues:
Code:


I will put PyQt4 libs for python 3.x and try there.

<edit>

filling test with loads of garbage still gives the same error.

Nah, turns out file size is actually important for the IPC mapping.
Code:
Should do the trick (assuming I computed that correctly). If it still doesn't work, double-check my math with struct.calcsize("8H165888pI") in your Python interpreter.

Same error. I have no idea what you mean by "struct.calcsize("8H165888pI")" (I am not a python person, sadly)

Still having issues
Code:
You really need a README here...

<edit>Running python3 fixed that, but now it has no idle background and has errors on all keys:

Code:


<edit>

I memset the VRAM in a test addin, and, well...

You drew a letter! Huzzah! I hope this means that text function emulation is coming soon.

Yes.

More yes. PrintXY is officially done, now to get other fonts working.
Added Bdisp_EnableColor, Print_OS, and locate_OS. Calling Bdisp_PutDisp_DD() without Bdisp_EnableColor(1) _will_ show up in C3 mode.

Awesome! Send pull requests early and often.

I need to debug input on Linux. It may be that grabbing keyboard focus isn't actually needed, but it seems there are a few things Qt does differently between Windows and Linux for input.

A question: How do I download the source for this project?

Or clone the repository with Mercurial:
Code: