Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
87 user(s) are online (58 user(s) are browsing Forums)

Members: 1
Guests: 86

hlt, more...

Support us!

Headlines

 
  Register To Post  

« 1 (2) 3 4 5 »
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
So far so good. When linking c++ with gcc 5.3.0, I get these link errors:

Quote:
ScratchHD:adtools-os4-20151223-268/ppc-amigaos/bin/ld: cannot find -lgcc
ScratchHD:adtools-os4-20151223-268/ppc-amigaos/bin/ld: cannot find -lgcc_eh


I have set up the compiler according to the readme. Is there anything else, that I am missing?

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@alfkil
I did a custom install of gcc 5.3.0 on my system so the only thing I can suggest is adding the path to libgcc.a to your ld search path to the link command line in your makefile with the -L option. On my system it would be something like " -L/SDK/gcc/lib/gcc/ppc-amigaos/5.3.0/newlib/lib/ " if you compile with newlib.

EDIT: Some of the coreutils in the adtools archive are reported to have some bugs so it might be better to use the coreutils from the SDK (SDK:local/C/).

Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@xenic

So far, so good... :)

Resized Image

What next?? ;)

Go to top
Re: Work on Qt 5.8 has begun :)
Home away from home
Home away from home


See User information
@alfkil
Quote:

What next?? ;)


To merge all your heavy aos4 native changes from 4.x ?:)

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@kas1e

:) Of course...

But first: Fix qmake!

Resized Image

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
Apparently, on AmigaOS

Quote:
mkdir("/some/existing/dir");


returns -1 (which is standard), but gives errno ENOSYS, which in sys/errno.h is described as

Quote:
#define ENOSYS 78 /* Function not implemented */


..instead of

Quote:
EEXIST 17 /* File exists */


How does that make sense?

Go to top
Re: Work on Qt 5.8 has begun :)
Just popping in
Just popping in


See User information
How fast does QT is performing compared to native functions, % of overhead?
Kamelito

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@alfkil

Which file system is this with?

If the CreateDir() call failed and IoErr() was set to ERROR_OBJECT_EXISTS then newlib will set errno to EEXIST.

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@alfkil
I just ran a quick test.
1. Created a test directory in ram: named "testdir".
2. Added these lines to a small utility program:
mkdir("ram:testdir");
printf("Error: %ld\n", errno);
3. Compiled the program and ran it with this result printed in the shell:
Error: 17

That's the expected result. One possibility for your result might be that errno is redefined somewhere in the Qt code. I have a ported library that contains this line:

#define errno Errno() // C library "errno" fails with sockets on some platforms

Because of that definition, errno always returns ENOSYS.



Edited by xenic on 2017/2/1 17:56:47
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@xenic

I messed it up a bit, sorry...

In fact, what was the problem is, that when using unix paths, and trying to create a root level entry (for instance '/MainHD'), you will be given an error code of ENOTDIR == 20 instad of EEXIST == 17.

Quote:

#include <unistd.h>
#include <sys/stat.h>
#include <stdio.h>
#include <errno.h>

int main()
{
if(mkdir("/MainHD", 0777) != 0)
printf("Error: %ld\n", errno);
return 0;
}


(To be built with '-lunix')

It is the same, if you try and mkdir("MainHD:", 0777);


Edited by alfkil on 2017/2/1 19:42:26
Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@alfkil

By the way, the linker issue has been solved. It is a simple matter of copying

Quote:

adtools-os4-20151223-268/lib/gcc/ppc-amigaos/5.3.0/lib/#?


to

Quote:

adtools-os4-20151223-268/lib/gcc/ppc-amigaos/5.3.0/newlib/lib/


Thanks! :)

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
Qt5 is configured and ready to build.

Resized Image

:)

Go to top
Re: Work on Qt 5.8 has begun :)
Not too shy to talk
Not too shy to talk


See User information
great :)

Go to top
Re: Work on Qt 5.8 has begun :)
Just popping in
Just popping in


See User information
@alfkil

We are waiting for: QupZilla :):)

Cross-platform Qt web browser.

https://github.com/QupZilla/qupzilla


Go to top
Re: Work on Qt 5.8 has begun :)
Home away from home
Home away from home


See User information
@alfkil
How easy was to go till that step, with knowing what you know from 4.7 porting time ? I mean was it easy enough second time in compare with how it was with 4.7 or everything was different ?

Join us to improve dopus5!
AmigaOS4 on youtube
Go to top
Re: Work on Qt 5.8 has begun :)
Quite a regular
Quite a regular


See User information

X1000|II/G4|440ep|2000/060|2000/040|1000
Go to top
Re: Work on Qt 5.8 has begun :)
Just popping in
Just popping in


See User information
@cha05e90

QupZilla ver. 1.4.4 for AmigaOS Qt 4.7.0 is very^2 old :(

PS.
QupZilla ver. =< 2.2 use OLD QtWebKit :(

QupZilla ver. >= 2.2 use NEW QtWebEngine :)

Go to top
Re: Work on Qt 5.8 has begun :)
Not too shy to talk
Not too shy to talk


See User information
@Alfkill

Yo!

Simone"Tuxedo"Monsignori, Perugia, ITALY.
Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
@kas1e

It is very easy :).

Go to top
Re: Work on Qt 5.8 has begun :)
Just can't stay away
Just can't stay away


See User information
What is the best way around changing calls to nanosleep() to something else on OS4?

Go to top

  Register To Post
« 1 (2) 3 4 5 »

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project