CMake progress

@alfkil

Nice! I hope to test it soon.

@Raziel

i'm using version 3.7.1

Linkage fixed. Now CMake 3.7.1 can build Qt apps on AmigaOS 4.1 :).



NB: I need to fix a small leakage, then it will be ready for release.

@alfkil
Quote:
AmiCygnix and some other Linux based program are setting the PATH variable to completely different text. I suggest you change the CMake PATH variable to CMPATH or something similar to avoid conflicts.

@xenic

Quote:

Don't be silly, there is only one PATH variable and in the first instance it's the PATH used by abc-shell to find programs, all other linux derived programs modify it to allow their required components to be found on the path.

That is why you should generally do somthing like

PATH="$PATH:/someextrapath/bin"

in a 'sh' script or sometimes.

setenv PATH "$PATH:/someotherpath/bin"

in a AmigaDOS script.

You can't set a CMPATH var instead as that will never be seen or interpreted by the abc-shell program.

@alfkil

Good to hear.

What about the requester for assign?

@AmigaBlitter

Gone :).
--
Here are the sources: https://www.dropbox.com/s/03r8ifomnw9l ... ake-3.7.1-source.lha?dl=0

Please do a non-case sensitive search for 'amiga' in this archive to see, what I have changed.
--
The release archive is in the os4depot upload queue.

Thanks for being with us :).

@broadblues
Quote:

I'm not a Linux user and not really aware that the PATH variable was only for the shell (abc-shell) and I have the abc-shell path set in SDK:Data/abc-shell/variables.

Here is the problem that made me think there as a conflict:

When I start AmiCygnix without setting a Cmake PATH variable I get this:

getenv PATH
/Cygnix/CygnixPPC/gtk2.24/bin:/Cygnix/CygnixPPC/local/bin:/Cygnix/CygnixPPC/bin:/Cygnix/CygnixPPC/X11R6.3/bin:/C

If I set the CMake PATH variable (using $PATH) before starting AmiCygnix like this:
setenv PATH "$PATH:/someotherpath/bin"

and then start AmiCygnix I get this:
getenv PATH
$PATH:/someotherpath/bin

Maybe my problem is with my AmiCygnix setup but it looked like a conflict to me.

@xenic

I think your problem is that $PATH was not set once before.

@alfkil

Thank you alfkil.

Thanks to you I will start the study where i finished (early bootstrapping cmake)

@xenic

Quote:

Primarialy for the abc-shell, other prgrams like CMake may manually traverse it to deterimine availablilty of programs to a build script etc.
Quote:

Mines in HOME:.abcrc but yes it's common to extend the default path in a startup shell.

eg:
PATH=".:/SDK/Local/C:/SDK/Local/newlib/bin:$PATH"

THis version will only be visible inside abc-shell.

Quote:

OK. this is because of two things, AmigaOS differ from bash / ksh in that iff FOO isn;t set then $FOO will in a string returns $FOO, in bash it would return "" (ie nothing).

Simplest solution to that bit is to set PATH either earlier in your user-startup (or in sdk-startup) or as a one off by doing

setenv save PATH = "/gcc/bin:/SDK/C:/C"

(that's the internal default of abc-shell, which will be why not setting it still works when no other PATH manipulators are out there)

The second would be that I'd guess that AmiCygnix startup only replaces the PATH if it's not set, so some fixing of the amicyngix startup might be required.

I dislike the amicygnix setup with avengence so don't have it installed here, so can't check whats going on specifically.

Afurther alternative would be to add the CMake path element to teh abc-shell variables PATH, but then you would have to ensure your always ran CMake from within abc-shell, but in many ways that could be tidier.

I recommend that cmake be statically linked (or bundle any shared object libs with it), since it's probably not gonna be too long before I update libcurl, and the .so filename might change.

@alfkil

First of all, thanks for working on CMake, it seems quite important tool today.

I tried to build SDL2 with it but first it crashed (could be my 64 kilobyte stack, because crash couldn't be reproduced with 100 kilobytes - maybe some stack cookie would be nice?).

After stack increase it started to give this error:



Anyone else seen this?

After some snooping, it looks like cmake is not able to Lock "make" command. Make still works from the same shell though, as usual.

If I copy make to my Cmake/bin directory, it proceeds, until failing with compiler check.

@Capehill

Have you set both the AmigaOS path and the PATH environment variable to be able to locate those entities? It needs to be able to find both cmake and gmake/make in both ways. Also, it should use gmake for unix path abilities, if it looks for make, it is a mistake.

@alfkil

I tried to follow the instructions. Below is my config and log.

@Capehill

The way it quotes "$PATH/something" in the snoopy output indicates, that your PATH env variable is not set correctly. Please reread the instructions and try again.

EDIT: As mentioned above - if your PATH variable has not been set previously, you need to leave out '$PATH' from your setenv command. So something like this:

setenv PATH /cmake/bin:/SDK/whatever/path/points/to/gmake

I'm sure, you can fill in the blanks ;).

@alfkil

Yeah, path was not set previously. However I don't see this in the instructions which I followed too literally. I have now something like:



and I can configure SDL2. So situation is looking better.

@Capehill

Fantastic! I am glad to hear. :)

Setting the stack to 128000 avoided the crash, but I was not able to configure a project yet.

@AmigaBlitter

Could you post the console output?