BUG Report and Question

[rallysjd]

Running 5.3, under Win 7-32: set the Explorer tab, and locate a sub-directory (let's call this lst) in a directory tree. Open Windows Explorer, and delete the sub-directory "lst". 5.3 still lists the directory, and sometimes will update itself after a few seconds. If I then click on the "lst" name in the 5.3 Explorer tab, 5.3 will usually lock up totally with a white screen, requiring the 5.3 process to be stopped. I had noticed in an earlier Codelite version a similar effect but had not identified the specific sequence of events.

I also have a possible problem with Win 8.1 (64 bit). Codelite 5.3 runs fine, and when I try building a working project from the Win 7 system, the first source file fails the build with Error 1, and make reports 0 errors, 0 warnings. I do get a .d (listing file) but no .o file. I have set the relevant output directories to full control, but there seems to be a problem writing the .o file. Have I found a bug? Is this Win 8 or Codelite?

All suggestions are appreciated!

SD

[rallysjd]

Found the "Make" bug under Win 8.1: a missing path to the gcc toolchain. Here's how I located it.

Open a Console window and set the path to your project source directory.
Assuming that you MakeFile is present and correct, type make
In my PC, make presented a messagebox informing me of a missing DLL that was in the gcc /bin directory.
Setting the missing path into the PATH list allows 'make' to do its job.

This path addition only remains valid while the console window is open. It's necessary to add this to the system
* open the Control Panel, select System-->Advanced Options and add the requires path to the PATH list.

Hope this helps others. Happy New Year to all.

SD

[eranif]

Open a Console window and set the path to your project source directory.
Assuming that you MakeFile is present and correct, type make

What were you trying to do, build codelite?

In my PC, make presented a messagebox informing me of a missing DLL that was in the gcc /bin directory.
Setting the missing path into the PATH list allows 'make' to do its job.

Not really related to codelite

This path addition only remains valid while the console window is open. It's necessary to add this to the system
* open the Control Panel, select System-->Advanced Options and add the requires path to the PATH list.

Altering system path is something I myself consider as bad practice. You should alter it for the current session of your CMD only

If you want to build codelite, look up for the instructions in our wiki
http://wiki.codelite.org

Eran