Messages - SkyIDE [ switch to compact view ]

Pages: prev1 ... 26 27 28 29 30 [31] 32 33 34 35 36 ... 50next
151
I've decided to possibly add more features for Beta 11. I am hoping to have them finished by the end of the week if I proceed with this.

I intend to add the following features in the Compile menu related to C++: "Compile Only", "Build Object Files" and "Specify Custom Linker". Other IDEs do this (except for Specify Custom Linker) but SkyIDE does not. Currently, the "Compile File" menu in SkyIDE compiles AND builds your files. Is there a need for a separate Compile and a Separate Build command? Please express your opinion. Personally, I never separately build the files. I am used to selecting "Compile" and the IDE does the job for me.

Also, I have created a "Specify Custom Linker" option where you will specify a custom linker to use or use the default one provided with the compiler.

Is there a need for all this so I start spending time on it or just leave it the way it is?


152
I am glad you solved your problem and I am sure Borland Technical Support was extremely helpful. Those guys are top notch!! They will never let you down. I don't know any other company so keen to help its customers.

153
Aha! It works! I just did "lcclnk test.obj" and voila! Thanks f0dder!

By the way, I had to change the code to printf("test") instead of cout, it's having problems with it. But yeah, as far as I know, LCC has a limited C++ support.

Thank You!

Hmmm now I have to modify some code......

154
Yes, sometimes I got exceptions too or it will just freeze.

155
Hi,

The support for LCC-WIN32 is fully completed but after all the work I did, I just realised the compiler might be buggy. It's either me doing something wrong or it is the compiler itself.

I have a simple code:


#include <iostream.h>




int main()
{

int iVar = 0;
cout << "Simple LCC C++ Program\n";

for (int i = 0; i < 1000; i++)
cout << "Looping\n";


return 0;

}

Filename test.cpp

I use "lcc test.cpp -FoC:\test.exe"
You can also use "lcc test.cpp -o C:\test.exe" which is the standard

The problem is, the exe file is produced BUT the program does not run. When you type C:\test.exe it just starts and exits instantly without producing any output. I have completely no idea why it does this. Their web site is:

http://www.cs.virginia.edu/~lcc-win32/

I didn't see any -l(inking) options. I was hoping I will find something but nothing.





Pages: prev1 ... 26 27 28 29 30 [31] 32 33 34 35 36 ... 50next
Go to full version