AFAIK, TinyCC only has standard C libraries, and some few Win32 extension. So it's not complete (compared to another compiler,like Pelles C). It's nice though

Regarding development of TinyCC: there have been a few updates to the CVS repository in the last four months, but nothing significant from what I can see. The mailing list still has a moderate amount of traffic, so it's not dead yet

I like the size and the simplicity of TCC.

Not that good:
- Relies on M$WCRT.DLL (or can I deactivate this effect / make "static" ??? )
- No DOS version / target

Do you have some static libc?

No idea where to search ... and how to use

that is the problem. If it should include some libc, it wouldn't be "tiny" anymore. Also writing such library is quite nasty job.

Maybe you could try to use static libc from MSVC (libcmt.lib)

OK ... thanks, but a solution of course should be at least LGPL ... and
not from M$.

What about LibCTiny ? Tested with Pelles C. Not sure about the other compilers.
http://www.wheaty.net/downloads.htm

Alternative for linux is diet libc

Well, I like the fact that TCC EXE's depend on MSVCRT.DLL.
Why?
Well, the EXE's are tiny. A simple hello world is 1,50kb.
Plus, the MSVCRT.DLL comes with all Windows OS.

And maybe you can link it static. (I never tried).


What I don't like about TinyCC is that it can't link resource files (I think).

You can't link MSVCRT.DLL static, but you can link the version of the MS CRT that comes with your copy of VC/VS statically... or use one if the tiny librarie (like Jibz' WCRT).

You can also link dynamically to whatever version of the MS CRT your compiler comes with - this does have the disadvantage of requiring redistributables, but gives you the advantage of the better code in the more recent libraries...

I've got VS 2005 Pro for free from my university.
Is it really worth uninstall the Express edition to install it? Will be there more features?
Also, i want to save some space. So uninstalling the Express Edition and the PSDK, and installing the VS 2005 Pro will be smaller installation?

Just found a link for the VS Orcas Beta download: http://www.microsoft.com/downloads/details.aspx?FamilyID=5d9c6b2d-439c-4ec2-8e24-b7d9ff6a2ab2&DisplayLang=en

ICC (Intel C Compiler) is also free for non-Comercial use. [Only the Linux version]

http://www.intel.com/cd/software/products/asmo-na/eng/340679.htm

What's the best way to get MS VC++ compiler only without IDE?

Hmm... MS just released free beta version of 2008 version:
http://msdn2.microsoft.com/pt-br/vstudio/default.aspx

Hi OzzY: I am a command-line-only VC user, and ended up getting it from the big one, last time from the same Orcas beta you mentioned above.

Previously there was (I think for MS VC 2003) a command-line-only release, but it's not worth.. if you want the latest. Orcas beta 1 fixed a nasty bug I reported to MS, which they weren't able to fix in time neither for VC2007 SP1 (although I reported immediately when SP1 public bugtests started), so I was forced to switch to Orcas (I had also tested Phoenix, and the bug wasn't present there, but Phoenix is a bit too much primitive for now - mind you, I think Orcas is based on Phoenix under the hood anyway, but it's much more "standard VC").

So, I think "the best way to get MS VC++ compiler only without IDE" as you asked is to get the full download and then strip everything but:

VC\bin (only part of)
VC\lib (only part of)
and if you need them, VC\include, etc..

You'll also need to grab MSVCR90.DLL and other DLL's (msvcp90.dll, msvcm90.dll, etc..) from the IDE directory.

I'd post my zipped dir, with the above work already done, but that would be illegal, so I cannot do it.

OzzY wrote:



COOL.

M$ Server wrote:

Hi Maverick!
I have a legal copy of VS 2005 Pro I got from school.
So, I installed it. I copy \bin, \lib and \include directories.
Where can I find the required DLLs? I don't understand what you mean by "from the IDE directory".

Thanks

I'm thinking about sticking to Pelles C for C and CodeBlocks+Mingw for C++. MSVC++ seems not really worth the bloat.
But I'll try to get only the compiler without the IDE to see how much space it requires.

Oh wow, i thought i was the only one, everyone criticizes me for it, but i find it far more efficient.


Provided you have downloaded orcas as suggested (i use vc 6 from the command line) you will find the required assemblies in C:\WINDOWS\WinSxS\. Look for folders that begin with x86_Microsoft.VC90 (i found four, as a i presume you will). Copy all 4 of these to your bin directory. Then take a look in C:\WINDOWS\WinSxS\Manifests. You will find a matching manifest for each of your assemblies beginning with x86_Microsoft.VC90. Copy these to your bin directory also. In order to have the windows loader acknowledge these copies, you will need to create a single side by side manifest telling it their location. Create a manifest in the bin dir called Microsoft.VC90.CRT.Manifest, and fill it thus:

You will need to alter the versions and the hashes to match what you find in each of the manifests from the Manifests folder you found in the WinSxS directory.
Next, take each of the runtime DLLs from their respective folders and place them in the root of the bin directory, along with the new manifest (you will not need the debug versions, nor the mfc or atl dlls, all i have is msvcr90.dll, msvcp90.dll and msvcm90.dll). After that's done, go to the Common7\IDE folder below the root of your install dir, and take mspdb80.dll and put it in your bin directory (it needs no manifest or anything like that). This should make your (command line only) visual c compiler totally portable (usable anywhere).

Hope this helps, Ehtyar.
P.S. To test it you can rename the manifests and the assembly folders inside of the WinSxS folder and run cl /? in your bin dir from the command line. If you have any problems or questions, don't hesitate to ask.