PureBasic Forums - English

I've got the source of jaPBe, and I'd like to compile it for myself.

It's proving tricky, though. I think I'm missing something silly.

Can anybody give me a brief overview?

Thanks.

Use original japbe from gpi
Use pb3.94 as compiler
copy scilexxer.dll to pb3.94\compilers

This needs gnozal!

Just in case no-one else offers the real solution, this is what I did on the few times (way back) I compiled it. (I fell on my face quite a bit trying to get it to work, and a lot of the following is redundant. I king-hit until it went down - no finesse at all )

1: Set up another instance of PureBasic. (Had a "Just for JaPBe" purebasic folder).

2: Copied the JaPBe sources into a working folder, well away from the JaPBe live folders.

3: Made sure scintilla was in the PureBasic compilers folder. (Actually, made sure scintilla was in any folder that might be significant, but think it is only needed in the compilers folder).

4: Renamed the main program from JaPBe.pb to something else. Not sure why, but that fixed something. (Maybe run-once, as I was using JaPBe to build JaPBe).

5: Copied across all the subfolders (except source) of the JaPBe folders and hung them from the working folder. There are some files that appear to be required.

Also copied across all the subfolders from the sources and hung them from the new JaPBe-only PureBasic compilers folder to get, for example, [YourUserPath]\Pure Basic\Compilers\Include and etc.

(This all in 3.94).

Some of the above is (obviously) redundant but maybe there are some clues. JaPBe seems to have quite a few tricks in it.

Fortunately, just when it looked like I would have to really learn it and do it myself for a v4, gnozal popped into a telephone booth and popped out again in Superman gear with JaPBe under one arm.


Edit:

Whup - ts-soft, that is all you did?

>> Whup - ts-soft, that is all you did?
yes
i have compiled the source from gnozal for testing surpose yesterday on this way

Strange. I get things like:

Include file not found:
C:\Program Files\Pure394japbe\compilers\Include\API-FileHandle.pbi

And unless I have sort of mirror images of everything under the "compilers" folder and under the working folder it will compile but performs badly.

But .. this is probably due to the imperfect meatware using this keyboard.

Thanks guys.

jaPBe is such a treasure trove of good code, and I want to make the most of it now in case it falls of the radar.

ts-soft wrote:Use original japbe from gpi
Use pb3.94 as compiler
copy scilexer.dll to pb3.94\compilers

That's it.
Nothing more, nothing less.

- you need a working PB 3.94 installation
- if you don't have it, install jaPBe 2.5.4.22 (last GPI version [for PB3.93])
- extract all the sources from jaPBeForPB400.7z into a folder
- open jaPBe.pb with jaPBe 2.5.4.22
(- eventually use cutter plugin to only include used procedures)
(- if you want to debug [F6], copy scilexer.dll to \compilers)
- compile

Any ideas why it doesn't know CHOOSECOLOURAPI in System.pbi.

I have a CHOOSECOLOUR structure, but not a CHOOSECOLOURAPI.

Am I missing a userlib?

Ok, I've managed to compile jaPBe for myself.

In addition to the above I had to rename the following structures:

• System.pbi : CHOOSECOLORAPI -> CHOOSECOLOR
  Print.pbi : PRINTDLGAPI -> PRINTDLG

I also had to set the Working Directory in the Project Options to the root jaPBE folder (in my case c:\program files\jaPBe)

Time to go exploring