Re: [Tinycc-devel] patch for tcc (and question)
> I'd say that this patch looks more like someone's personal easter egg,> or at > least you missed to explain why you would recommend other people > to use an install structure as you do as well, what the benefit is over > the one that they already have, and how they are supposed to create it, > preferably automatically I'd assume... Right. > Other than that it is already possible to install the tcc executable(s) > in a custom separate location, for example like > > ./configure --tccdir=... --bindir=... > > which is supposed to set CONFIG_TCCDIR explicitly and thus override the > run-time automatism under libtcc.c:98: #ifndef CONFIG_TCCDIR.It does if you > can run a shell script, yes. Still, that creates a static path,and when did > those become the norm? > "As a general rule, your messages should start with a single lineGot it. --Fred ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] patch for tcc (and question)
> Where is this path allocation freed?When the program exits. It is allocated > once at program startup, andthen auto-freed at program termination. But, > sure, I could add a free. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] patch for tcc (and question)
On 27.05.2023 02:28, Fred van Kempen via Tinycc-devel wrote: Herman: >> Based on the 0.9.27 release code, I added a patch to tcc.c to let it "find" itself and its >> support directories (include, lib etc) even it is not located in the root of that setup. I >> normally have stuff organized under "bin/" to keep it clean, and because my systems >> require several platforms, it is usually like > the mob branch? > I am missing the patch? Submitted with ID da3a763. I'd say that this patch looks more like someone's personal easter egg, or at least you missed to explain why you would recommend other people to use an install structure as you do as well, what the benefit is over the one that they already have, and how they are supposed to create it, preferably automatically I'd assume... Other than that it is already possible to install the tcc executable(s) in a custom separate location, for example like ./configure --tccdir=... --bindir=... which is supposed to set CONFIG_TCCDIR explicitly and thus override the run-time automatism under libtcc.c:98: #ifndef CONFIG_TCCDIR. By the way, from https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project "As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation." (with also no more than about 50-70 characters each line) -- gr --Fred ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] patch for tcc (and question)
This leaks under Windows https://github.com/TinyCC/tinycc/actions/runs/5096032862/jobs/9161538015 Where is this path allocation freed? https://github.com/TinyCC/tinycc/commit/da3a763e977a84edf43c5ca101deae768ae8480d#diff-cad896f916760198e667f0d877f6dc0b49593abd8c57308f970763e3698424fbR139 cheers, From: tinycc-devel-bounces+wqweto=gmail@nongnu.org [mailto:tinycc-devel-bounces+wqweto=gmail@nongnu.org] On Behalf Of Fred van Kempen via Tinycc-devel Sent: Saturday, May 27, 2023 3:29 AM To: Herman ten Brugge via Tinycc-devel Cc: Fred van Kempen Subject: Re: [Tinycc-devel] patch for tcc (and question) Herman: >> Based on the 0.9.27 release code, I added a patch to tcc.c to let it "find" >> itself and its >> support directories (include, lib etc) even it is not located in the root of >> that setup. I >> normally have stuff organized under "bin/" to keep it clean, and because my >> systems >> require several platforms, it is usually like > the mob branch? > I am missing the patch? Submitted with ID da3a763. --Fred ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] patch for tcc (and question)
Herman: >> Based on the 0.9.27 release code, I added a patch to tcc.c to let it "find" >> itself and its >> support directories (include, lib etc) even it is not >> located in the root of that setup. I >> normally have stuff organized under >> "bin/" to keep it clean, and because my systems >> require several >> platforms, it is usually like > the mob branch? > I am missing the patch?Submitted with ID da3a763. --Fred ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] patch for tcc (and question)
On 5/17/23 23:28, Fred van Kempen wrote: Hello list: I hope the list is still active... development seems to have stopped, or at least stalled? Based on the 0.9.27 release code, I added a patch to tcc.c to let it "find" itself and its support directories (include, lib etc) even it is not located in the root of that setup. I normally have stuff organized under "bin/" to keep it clean, and because my systems require several platforms, it is usually like .../ /bin/ /x86 /tcc.exe /x64 ... /include /lib/ /x86 /libtcc-32.a and so on. So, the patch allows tcc.exe to be in "below" the root folder, and still find things, by looking for the presence of an include/ directory. Is this something I could (or even should ;-) push to the mob branch? I am missing the patch? Is this against 0.9.27 or against mob? Sorry cannot answer your question. I have no arm/arm64 windows. Herman ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
