delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2012/11/15/19:01:56

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=Wuvmq9M8zldwF1wTdDIEpZscUphPDl/uhFG4osbR/R8=;
b=GVF9Apfzm3g8G4ZCqCZTn6WYFXECv7vFXTCViTjLla1IinqolF2/Q4TM0/7dy5bhkj
jWGnCWa2VpZYOYRXEc+E5S/9g+XsBMj3tbHe/UdRz1ojDhw2ZbZgZgGdeUOxmmbD6tLd
LjgOUWQx0F67KQ33MeOwNpYVXLm3veeQ/8rlScyea50cHCIVL6hV8iSiM+96I7YBq+zM
slTxPA9Al+W6YgWsV5NtYjSvkmx6ADuZ1gK+XBY5wlEbNnjuCETHzyu8g63wVS66Ssyy
4nwrRDajprPrMcURgac4ua/h36l/fhuPP7VUM0MoEDOJkPjXw2uOyH5+8uIlPOs/3VNw
eWUQ==
MIME-Version: 1.0
In-Reply-To: <20121115210903.90A4881345E3@turkos.aspodata.se>
References: <20121113211401 DOT 20747813A49B AT turkos DOT aspodata DOT se>
<CAOuGh89nhtaPkKZ+0CJGn9V_XnZyi6YD-NndT53FHoAyYD0LFw AT mail DOT gmail DOT com>
<20121115210903 DOT 90A4881345E3 AT turkos DOT aspodata DOT se>
Date: Thu, 15 Nov 2012 19:01:02 -0500
Message-ID: <CAPYb0EE-xqA681-iq9AwnL7Wq1j9NL7AP383X5qe5QeCZZW0Ug@mail.gmail.com>
Subject: Re: [geda-user] Bug #903129 Translations don't work on Windows
From: Bob Paddock <bob DOT paddock AT gmail DOT com>
To: geda-user AT delorie DOT com
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> Ok, let's rephrase a, to
>
> a, Tell the user <as above>
>    else he has to build from source.
>
> would that work ?

No.  Few users of Windows are developers.
They would not even have a compiler let alone know what to do with it.

> or the code could just do MS-windows equivalent of
>
> char localedir[100] = "C:\\some\\path";
> int cc;
> for (cc = 'C'; cc < 'Z'; cc++) {
>         struct stat sbuf;
>         localedir[0] = cc;
>         if (!stat(localedir, &sbuf) && S_ISDIR(&sbuf) {
>           break;
>         }
> }

That will take a long time as it will have to wait for each
non-existent network maped drive to fail.
Even local drives could take time to fail depending on the version of
Windows and their drivers.

> May the user still be able to build programs on such a system?

Things do seem to be going in the direction of preventing that, tho we
are not there yet.

> If so, the install script might do a "final link" of the lib adding and
> compiling a simple 'const char libgeda_locale[] = "..."' source file to the
> lib, then *sign* it and install it. Would that be possible?

Could be done that way.  Some USB open-source USB drivers take the
approach of self-signing.
That may not work some time in the future, I'd not worry about it today.

>> d. is the most Windows viable solution.

> I haven't found anything c++ish in libgeda, should we still worry?

Not today.

> How do other programs handle this?

I usually use the wxWidgets package for my Windows code and it has
'standard paths':
http://docs.wxwidgets.org/2.8/wx_wxstandardpaths.html
http://docs.wxwidgets.org/2.9.4/classwx_standard_paths.html


> So a fourth possibility could be:
>
> e, install geda things in some dir, so:

As long as 'dir' is not hard coded that is fine.
Installers will generally take care of setting that.

>   the binaries are in dir\bin
>   locale files are in dir\share\locale

That works.

BTW.  It is best to use forward slashs in source files for paths in
source files.
It is the Windows command processor that has issues with '/'.
#include "x\y.h" works just as well as #include "x/y.h".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019