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

[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.

[fullmetalcoder]

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.

What do you mean by "traverse the code" ?

I am finding it painful to find the bug. Just make a change and then recompile it again which takes about 10 mins.

Which files did you change to get such a long re-compilation? Make normally keep track of dependencies between files to reduce compilation time once an app has been build once...

I was just wondering if there's a fast way of doing the debugging?

It depends on what you mean... Once you have compiled the app in debug mode all you need is to run it within gdb... Note that you can also run an app not build in debug mode within gdb but the output of some commands will be trickier to understand (backtrace for instance) and some commands won't even work... It should anyway be enough to track down the place where Edyuk fails...

[fullmetalcoder]

Hi all,

After some long days of struggle with model/view quirks, line endings and other tricky issues I've come to something much more stable. Yet, before releasing a package I'd like some tests to be done on other platforms than just UNIX/Linux.

The code is available through SVN : https://edyuk.svn.sf.net/svnroot/edyuk/0.9.0

As I know most Win32 users are not familiar with SVN, a package is available as well...

[vermarajeev]

I tried running edyuk but get this error

/home/rajeev/Desktop/edyuk-0.9.2 # ./build -r
 
 --- Checking configuration ---
Qt version    :                 [OK] 4.2.1
qmake command :                 [OK] qmake
 --- Configuration successful ---
 
 --- Building Edyuk ---
Moving to directory src/lib
Moving to directory src/exec
Moving to directory src/default
 --- Compilation successful ---
 
application edyuk not found after trying :
/home/rajeev/Desktop/edyuk-0.9.2/./edyuk.bin
./edyuk.bin

/home/rajeev/Desktop/edyuk-0.9.2 # ./build -r

 --- Checking configuration ---
Qt version    :                 [OK] 4.2.1
qmake command :                 [OK] qmake
 --- Configuration successful ---

 --- Building Edyuk ---
Moving to directory src/lib
Moving to directory src/exec
Moving to directory src/default
 --- Compilation successful ---

application edyuk not found after trying :
/home/rajeev/Desktop/edyuk-0.9.2/./edyuk.bin
./edyuk.bin

To copy to clipboard, switch view to plain text mode 

[fullmetalcoder]

I tried running edyuk but get this error

/home/rajeev/Desktop/edyuk-0.9.2 # ./build -r
 
 --- Checking configuration ---
Qt version    :                 [OK] 4.2.1
qmake command :                 [OK] qmake
 --- Configuration successful ---
 
 --- Building Edyuk ---
Moving to directory src/lib
Moving to directory src/exec
Moving to directory src/default
 --- Compilation successful ---
 
application edyuk not found after trying :
/home/rajeev/Desktop/edyuk-0.9.2/./edyuk.bin
./edyuk.bin

/home/rajeev/Desktop/edyuk-0.9.2 # ./build -r

 --- Checking configuration ---
Qt version    :                 [OK] 4.2.1
qmake command :                 [OK] qmake
 --- Configuration successful ---

 --- Building Edyuk ---
Moving to directory src/lib
Moving to directory src/exec
Moving to directory src/default
 --- Compilation successful ---

application edyuk not found after trying :
/home/rajeev/Desktop/edyuk-0.9.2/./edyuk.bin
./edyuk.bin

To copy to clipboard, switch view to plain text mode 

For an unknown reason make doesn't seem to respect return value conventions (or maybe I badly checked for a 0 return value in the script...). Anyway the "compilation successfu" message is not to be trusted unless you show other message about the ongoing build process (such as "Compiling x.cpp", "moc'ing X.H" and "Linking x.so"...). Hopefully the script creates a log file (.compile.log) that you'll find in the main directory and which should explain why compilation failed...

edit : did you check the content of the folder once you had built Edyuk? It just occured to me that I might I left debug as default build mode... Try this command instead of ./build -r :
$ ./edyuk_debug

[vermarajeev]

Try this command instead of ./build -r :
$ ./edyuk_debug

Yep that works. We'll let you know if any error.

By the way, I just see your profile as fullmentalcoder, can I know your unidentified name.

[fullmetalcoder]

Yep that works. We'll let you know if any error.

Good! I'm looking forward to hearing your comments

By the way, I just see your profile as fullmentalcoder, can I know your unidentified name.

I thought it was fullmetalcoder (no 'n') If you search a bit you won't have troubles to find my name (have a look at the contest page for instance...)

[vermarajeev]

Hi Luc,
I started using edyuk, I was able to load a project. The IDE is really good. CONGRATS...

I have a problem debugging my programs. I followed these steps.
1) Open the .pro file.
2) Then I couldn't find any shortcut to place a breakpoint, so did by right clicking
3) clicked Debug->Start Debugging
4) Get this error from the Debug.log displayed at bottom

---------- process gdb started ----------
[/home/rajeev/Desktop] gdb --quiet --fullname /home/rajeev/Desktop/edyuk-0.9.2
/home/rajeev/Desktop/edyuk-0.9.2: No such file or directory.
(gdb) start
No symbol table loaded. Use the "file" command.
(gdb) continue
The program is not being run.
(gdb)

Any idea???

One more thing,
In windows, we have shortcuts to
1) place a breakpoint
2) run the debugger with F5
3) Go to next step using F10
etc etc. The life of user is made much easier, rather than going and doing all other stuffs. Cant we provide shortcuts to make Edyup a more user friendly in terms of debugging.

Thanks