Path: ...!fu-berlin.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Vir Campestris Newsgroups: comp.lang.c Subject: Re: Baby X is bor nagain Date: Wed, 26 Jun 2024 11:54:00 +0100 Organization: A noiseless patient Spider Lines: 20 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 26 Jun 2024 12:54:02 +0200 (CEST) Injection-Info: dont-email.me; posting-host="33717825154947d0235c868c3b1181dd"; logging-data="2209018"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/FAPcj8WT+EyDV3aQauSm+VE5I7Rj4WSk=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:iicnnZRT8droOvV703hGZ4sr8OA= Content-Language: en-GB In-Reply-To: Bytes: 2331 On 24/06/2024 14:01, bart wrote: >> > > Then people have different concepts of what a 'build' is. > > My definition is a full translation from source code to executable > binary. That, I have never had any trouble with for my own projects, and > have never had to hang about for it either, because I define and control > the process (and most often write the necessary tools too, AND design > the language involved to that end). > To me that is part, but not all, of a build. At the very least (at least, for production code) there will be some kind of packaging. And I really hope you have some automated tests to run. Which also count as part of the build process. Andy