[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Problem with libtcc DLL + MEMORY output

From: Amaury Bouchard
Subject: Re: [Tinycc-devel] Problem with libtcc DLL + MEMORY output
Date: Tue, 29 Nov 2016 14:57:47 +0100

Indeed, I missed this information. Thank you for your help.
Well, I found some documentation where the tcc_set_output_type() function was called after compilation, and it work fine like that, so I didn't wonder that TCC was not able to do both outputs with a single compilation. The question about why I would want to do that is not relevant; in some situation, it could be useful to not compile again and again the same piece of code, but it was more of an experiment in my case.

Thanks again.

Date: Mon, 28 Nov 2016 19:38:58 +0100
From: grischka <address@hidden>
To: address@hidden
Subject: Re: [Tinycc-devel] Problem with libtcc DLL + MEMORY output
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Amaury Bouchard wrote:
> Hi all,
> So, nobody here ever tried to use TinyCC library to compile some code, then
> generate a .so/.dll file, then execute this code?

Why would anyone want to do that?

Just in case, there is a comment for tcc_set_output_type()" in both
libtcc.h and the libtcc_test example:

     /* set output type. MUST BE CALLED before any compilation */

I suppose you have seen it but wanted to see what happens if you ignore
it, and the answer is the one that you already have:  does not work.

As with all software there are things within its scope and things beyond
its scope and decisions were made depending on usefulness and required

-- gr

reply via email to

[Prev in Thread] Current Thread [Next in Thread]