Edyuk : fully-featured, highly flexible and free cross-platform IDE

[fullmetalcoder]

Edyuk 0.9.1 has just been released. It is mainly a bugfix release which, above all, fixes compilation under Windows.

https://sourceforge.net/project/show...ease_id=512221

[fedcer]

Hi, I'm trying to build Edyuk 0.9.1 but I'm getting the following errors:

Processing form ui/createnewdialog.ui
Compiling ../../3rdparty/qpool/qpool.cpp
../../3rdparty/qpool/qpool.cpp:105: error: cast from 'QPool*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:106: error: cast from 'char*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:106: error: cast from 'char*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:106: warning: format '%x' expects type 'unsigned int', but argument 5 has type 'long unsigned int'
../../3rdparty/qpool/qpool.cpp:223: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:223: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:223: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:223: warning: format '%x' expects type 'unsigned int', but argument 4 has type 'long unsigned int'
../../3rdparty/qpool/qpool.cpp:223: warning: format '%i' expects type 'int', but argument 5 has type 'size_t'
../../3rdparty/qpool/qpool.cpp:248: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:248: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:248: error: cast from 'size_t*' to 'int' loses precision
../../3rdparty/qpool/qpool.cpp:249: warning: format '%x' expects type 'unsigned int', but argument 4 has type 'long unsigned int'
../../3rdparty/qpool/qpool.cpp:249: warning: format '%i' expects type 'int', but argument 5 has type 'size_t'
../../3rdparty/qpool/qpool.cpp:249: warning: format '%x' expects type 'unsigned int', but argument 7 has type 'size_t'
../../3rdparty/qpool/qpool.cpp:249: warning: format '%x' expects type 'unsigned int', but argument 8 has type 'long unsigned int'

and the list of erros continues with more errors of that same kind.

[fullmetalcoder]

Hi, I'm trying to build Edyuk 0.9.1 but I'm getting the following errors:

and the list of erros continues with more errors of that same kind.

It looks like your compiler is very strict with casts... Apparently I forgot comment out all the qDebug() statements I put in the QPool code and your compiler complain. All you have to do is opening src/3rdparty/qpool/qpool.cpp and comment out the concerned lines... Apologies for this...

[srikpen]

I am getting the following when compiling with the follow error in the following env:

windows 2000 sp4
Qt 4.3.0
C:\qtwork>mingw32-make -v
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.


C:\qtwork\edyuk-0.9.1>build
...
...
.\..\..\Qt\4.3.0\mkspecs\win32-g++" -o ..\tmp-default-4.3.0-win32\obj\release\qm
akevariable.o qmakemodel\qmakevariable.cpp
../../3rdparty/qprojectmodel/qprojectparser.h: In member function `void QProject
Parser::qt_check_for_QOBJECT_macro(const T&) const [with T = QMakeParser]':
../../../../Qt/4.3.0/include/QtCore/../../src/corelib/kernel/qobject.h:411: in
stantiated from `T qobject_cast(QObject*) [with T = QMakeParser*]'
qmakemodel\qmakevariable.cpp:654: instantiated from here
../../3rdparty/qprojectmodel/qprojectparser.h:38: error: void value not ignored
as it ought to be
mingw32-make[1]: *** [..\tmp-default-4.3.0-win32\obj\release\qmakevariable.o] Er
ror 1
mingw32-make[1]: Leaving directory `C:/qtwork/edyuk-0.9.1/src/default'
mingw32-make: *** [release] Error 2

I tried that thing on google
Re: patched!
06/01/2007, 2:28 on content: Edyuk
some little error
must be:

3dparty/qprojectmodel/qprojectparser.h:

#ifndef _QPROJECT_PARSER_H_
#define _QPROJECT_PARSER_H_
 
#define QT_NO_QOBJECT_CHECK 1
 
#include "qproject.h"

#ifndef _QPROJECT_PARSER_H_
#define _QPROJECT_PARSER_H_

#define QT_NO_QOBJECT_CHECK 1

#include "qproject.h"

To copy to clipboard, switch view to plain text mode 

but no luck there still same error as above.

thanks.

[fullmetalcoder]

I tried that thing on google
Re: patched!
06/01/2007, 2:28 on content: Edyuk
some little error
must be:

3dparty/qprojectmodel/qprojectparser.h:

#ifndef _QPROJECT_PARSER_H_
#define _QPROJECT_PARSER_H_
 
#define QT_NO_QOBJECT_CHECK 1
 
#include "qproject.h"

#ifndef _QPROJECT_PARSER_H_
#define _QPROJECT_PARSER_H_

#define QT_NO_QOBJECT_CHECK 1

#include "qproject.h"

To copy to clipboard, switch view to plain text mode 

but no luck there still same error as above.

thanks.

There are two things left to try :

• add DEFINES += QT_NO_QOBJECT_CHECK to config.pri (dirty hack)
• add Q_OBJECT to QMakeParser declaration in src/default/qmakemodel/qmakeparser.h

If it still fails please let me know. I should anyway release a newer package soon.

[srikpen]

There are two things left to try :

• add DEFINES += QT_NO_QOBJECT_CHECK to config.pri (dirty hack)
• add Q_OBJECT to QMakeParser declaration in src/default/qmakemodel/qmakeparser.h

If it still fails please let me know. I should anyway release a newer package soon.

Thanks a lot.

adding the Q_OBJECT solved the problem without the dirty hack you mentioned.

With support like this I don't mind being santa's elve for any testing req's on
my triple boot windows 2K, fedora 6 AMD 32-bit, 64-bit system.

How do I build this in debug mode as well, where do the logs go ??
regards
sri.

[fullmetalcoder]

adding the Q_OBJECT solved the problem without the dirty hack you mentioned.

This was the clean solution. I mentioned the other one as well because some people happen to be quite lazy...

With support like this I don't mind being santa's elve for any testing req's on
my triple boot windows 2K, fedora 6 AMD 32-bit, 64-bit system.

It's very kind of you

How do I build this in debug mode as well, where do the logs go ??

Edit config.pri... You can basically do any find tunning you want in it since it is included by all subdirs. You'll just need to replace CONFIG += release by CONFIG += debug. There used to be a way to redirect debug output to a log file but I think I dropped it... You can anyway bring it back by editing src/lib/edyukapplication.cpp and adding appropriate code within the message handler.

[srikpen]

After running edyuk-debug I am not able to find the run.log anywhere.
I have diffed the edyukappliation with it's original as below, is it some thing else I am missing?

C:\qtwork\edyuk-0.9.1\src\lib>diff edyukapplication.cpp edyukapplication.cpp.ORG
75c75
< static QTextStream cout(stdout), cerr(stderr), clog;
---
> //static QTextStream cout(stdout), cerr(stderr), clog;
93c93
<       clog << type[t] << msg << endl;
---
>       //clog << type[t] << msg << endl;
98c98
<               clog << "aborting..." << endl;
---
>               //clog << "aborting..." << endl;
142c142
<       clog.setDevice(pEdyukLogFile);
---
>       //clog.setDevice(pEdyukLogFile);

C:\qtwork\edyuk-0.9.1\src\lib>diff edyukapplication.cpp edyukapplication.cpp.ORG
75c75
< static QTextStream cout(stdout), cerr(stderr), clog;
---
> //static QTextStream cout(stdout), cerr(stderr), clog;
93c93
<       clog << type[t] << msg << endl;
---
>       //clog << type[t] << msg << endl;
98c98
<               clog << "aborting..." << endl;
---
>               //clog << "aborting..." << endl;
142c142
<       clog.setDevice(pEdyukLogFile);
---
>       //clog.setDevice(pEdyukLogFile);

To copy to clipboard, switch view to plain text mode 

BTW the debug edyuk justs shows up in task manager and no GUI comes up, then terminates after a few seconds. Any Idea?
Just set the debug options as you mentioned i.e.:
CONFIG += debug and
add Q_OBJECT to QMakeParser declaration in src/default/qmakemodel/qmakeparser.h

[fullmetalcoder]

After running edyuk-debug I am not able to find the run.log anywhere.
I have diffed the edyukappliation with it's original as below, is it some thing else I am missing?

C:\qtwork\edyuk-0.9.1\src\lib>diff edyukapplication.cpp edyukapplication.cpp.ORG
75c75
< static QTextStream cout(stdout), cerr(stderr), clog;
---
> //static QTextStream cout(stdout), cerr(stderr), clog;
93c93
<       clog << type[t] << msg << endl;
---
>       //clog << type[t] << msg << endl;
98c98
<               clog << "aborting..." << endl;
---
>               //clog << "aborting..." << endl;
142c142
<       clog.setDevice(pEdyukLogFile);
---
>       //clog.setDevice(pEdyukLogFile);

C:\qtwork\edyuk-0.9.1\src\lib>diff edyukapplication.cpp edyukapplication.cpp.ORG
75c75
< static QTextStream cout(stdout), cerr(stderr), clog;
---
> //static QTextStream cout(stdout), cerr(stderr), clog;
93c93
<       clog << type[t] << msg << endl;
---
>       //clog << type[t] << msg << endl;
98c98
<               clog << "aborting..." << endl;
---
>               //clog << "aborting..." << endl;
142c142
<       clog.setDevice(pEdyukLogFile);
---
>       //clog.setDevice(pEdyukLogFile);

To copy to clipboard, switch view to plain text mode 

The log file should be placed in Edyuk::settingsPath() which should expand to ~/.Edyuk-$version$/ so in your case ~/.Edyuk-0.9.1 (or ~/.Edyuk-1.0.0-alpha in case you use the SVN trunk)

BTW the debug edyuk justs shows up in task manager and no GUI comes up, then terminates after a few seconds. Any Idea?

It might come from an assert failure... You know Qt uses a lot of Q_ASSERT() macro everywhere and it can result in very different behaviours of debug and release builds... The best way to figure out what's wrong is to run on command line or under gdb. This way you'll know why the debug build fails and we'll be able to fix this

[srikpen]

Sorry for bothering you much. But I am not a windows guy.
with gdb I'm comfortable on linux.

I feel impaired with the windows thing.
You have any idea how I can get started debugging this with proper tools on windows.
I don't want to start configuring tools to get running, some quicky debugger, ctags(or find, grep) kind of thing on windows?

Just wanted to know, I see you're also not a windows guy but thought you might have some idea.

thanks
sri.

[fullmetalcoder]

Sorry for bothering you much. But I am not a windows guy.

I'm a little lost here? Do you mean you're testing under Window$ and facing troubles there that you don't know how to handle?

You have any idea how I can get started debugging this with proper tools on windows.
I don't want to start configuring tools to get running, some quicky debugger, ctags(or find, grep) kind of thing on windows?

Just wanted to know, I see you're also not a windows guy but thought you might have some idea.

Sure! gdb is also available under Window$. You don't need ctags to use Edyuk code completion but I think it is available for Win as well. As for grep/find and other *nix tools I don't think there is any equivalent but you can always have a look at Cygwin...

Hope this helps

[srikpen]

Yep I don't know how to traverse the code fast on Windows. I am using gvim for windows. I will try to find the equivalent ctags and also the gdb.

I am finding it painful to find the bug. Just make a change and then recompile it again which takes about 10 mins.
I was just wondering if there's a fast way of doing the debugging?

thanks much.

[fedcer]

It looks like your compiler is very strict with casts... Apparently I forgot comment out all the qDebug() statements I put in the QPool code and your compiler complain. All you have to do is opening src/3rdparty/qpool/qpool.cpp and comment out the concerned lines... Apologies for this...

Thanks, now it copiled fine. By the way, congratulations ! It is a very good IDE.

[fullmetalcoder]

Thanks, now it copiled fine.

Good news!

By the way, congratulations ! It is a very good IDE.

Thanks a lot Such feedback is very important when I feel lost within the sources with so many things left to do and so little time to deal with them