From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) by sourceware.org (Postfix) with ESMTPS id 5ECBE383EB06 for ; Fri, 9 Dec 2022 16:40:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5ECBE383EB06 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=foss.st.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=foss.st.com Received: from pps.filterd (m0046660.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 2B9EmVYV018838; Fri, 9 Dec 2022 17:40:38 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=selector1; bh=4O73QSJ01NaGsmM4u8jwpCYI3KPS5/PjPovtwjGYLiQ=; b=V74X8mfjwkhEIfrHhniqP9gjO0srFwskzLEk9m/LgyjgVKAWwl0l8JMPh8yYJCQJebnn Gu6CQQHtIcHjt5B+ACGpLm4UKYZJaQ110wpVvJ4cA/URfbjFRec+DbEMmGbCutDe235h /9jtTbbIHiv++l1gyc+B16ZxxY/q9NDoeg+UcACUJoyv6+O/HH52BtZjmzfk/N+4rRP4 Q7kkcNeZnDR2UB/6mJiZuIcLCoVGatPl9EnsIJfWoh7g93bzETNUqE9FH5Zs4u4vy7Xv dk/HhCTItBBoOigG9t8VJMd6xWhiMsFODgegRFE/qqdm8PJ0C0J3cR0HWtDsnqsvRWZt iw== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com (PPS) with ESMTPS id 3mbwb94qf1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 09 Dec 2022 17:40:38 +0100 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id CC70110002A; Fri, 9 Dec 2022 17:40:32 +0100 (CET) Received: from Webmail-eu.st.com (shfdag1node3.st.com [10.75.129.71]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 9BF23235F18; Fri, 9 Dec 2022 17:40:32 +0100 (CET) Received: from [10.252.28.108] (10.252.28.108) by SHFDAG1NODE3.st.com (10.75.129.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.13; Fri, 9 Dec 2022 17:40:31 +0100 Message-ID: <7cc5a9de-bd1c-4994-63ff-565a8f0de85b@foss.st.com> Date: Fri, 9 Dec 2022 17:40:30 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: Iconv.html and iconv.html Content-Language: en-US To: Mike Frysinger CC: Newlib References: <419fd802-0895-3c9e-dd0d-be9963d7a83b@foss.st.com> From: Torbjorn SVENSSON In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.252.28.108] X-ClientProxiedBy: SHFCAS1NODE1.st.com (10.75.129.72) To SHFDAG1NODE3.st.com (10.75.129.71) X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.923,Hydra:6.0.545,FMLib:17.11.122.1 definitions=2022-12-09_09,2022-12-08_01,2022-06-22_01 X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Mike, On 2022-12-09 17:29, Mike Frysinger wrote: > On 02 Dec 2022 17:06, Torbjorn SVENSSON wrote: >> I have been building a toolchain for the arm-none-eabi target using a >> rather recent snapshot of newlib. While building the html documentation, >> I noticed that there will be generated the two files named Iconv.html >> and iconv.html. >> While this works fine for case sensitive file systems, it's obvious that >> this will not have the desired outcome on a case-insensitive file >> system, such as on Windows system. >> >> The Iconv.html file contains the chapter description and the iconv.html >> file contains the description of the iconv-function. >> >> Can someone, with the knowledge of how these filenames are generated, >> change one of them so that the filenames differ on a case insensitive >> file system? > > the naming is straightforward -- the @node attribute is turned directly into > the filename. we use @node Iconv for the chapter and @node iconv for the C > function APIs. so the fix is to change one of them. > > the sub-areas have a 1-to-1 mapping to the chapter (e.g. stdio/->Stdio, > iconv/->Iconv, etc...). the generated APIs similarly map source file > names to the chapter (e.g. iconv.c->iconv, strncmp.c->strncmp). but they > can map any number of functions inside those source files, and we might > rename them as makes sense in general for our organization. so i'm more > inclined to change the generated API chapters, and do it across the board > instead of a one-off for iconv.c. > > anyone want to bikeshed the naming convention ? gen_xxx ? src_xxx ? > there doesn't seem to be a standard here in the GNU toolchain space that > i can see. bfd/ has a conflict, but they just do a one-off rename with > bfd.texi->bfdt.texi for the makedoc output. To me, I think "gen_xxx" is preferred in that case. I think GDB has another of those conflicts (that is still to be solved) with qMemTags vs QMemTags. Kind regards, Torbjörn