[Top][All Lists]

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

Re: [Tinycc-devel] New configure arguments?

From: Barath Aron
Subject: Re: [Tinycc-devel] New configure arguments?
Date: Tue, 16 May 2017 19:12:28 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1

On 05/16/2017 01:34 PM, grischka wrote:
Barath Aron wrote:

It is okay to add a few extra configure arguments [1]?
I'm working on an OS that does not support a few features (yet). Such as: long double, stuff needed for "tcc -run" and stuff needed for bound check.

I'd say general unspoken requirement for commits to tinycc git
is a certain public interest.
That implies...?

So, my solution is to disable them during the configuration. I have a patch for that, but I don't want to commit it until I know it is okay or not.

+  --no-long-double) no_long_double="yes"
+  ;;

Sigh, a few days ago I committed a patch that removed most of
those variables in favor of the single "confvars" list.
I saw that patch, I put the old version of my patch into the mail. The "new" version just put some elements into the "confvars". Then adds the "-D"s to NATIVE_DEFINES in the Makefile.

Experts might just do this:

I guess it is not a problem to stuff the code with the related #ifdefs?

Also you might create a "config-cross.mak" (see make help)
with contents

    DEF-x86_64 += -DCONFIG_LDOUBLES=0

(Hm, maybe a reason to rethink the name "config-cross.mak")
The "config-cross.mak" seems to be a good idea, but previously I was a bit confused on its name.
But I'll use it if this is the "way" to do it. :)
To be honest, I wasn't a big fan of extending the configure with all these stuff. Takes too much effort for those little things. ;)

--- grischka

Tinycc-devel mailing list


reply via email to

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