Waldemar Rosenbach [EMAIL PROTECTED] writes:
But what is the best way to deal with the platform depend stuff in the
interface?
A platform independent interface!
--
Ralph
Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
Suggestions so far are to put this information in the source
filename. For instance teaching Automake to install
`pt_BR-foo.1' or `foo.1.pt_BR' as `pt_BR/man1/foo.1',
with the rewriting issues Josef pointed out.
`foo.1.pt_BR' breaks Emacs'
7,600,000 E-MaiLe BeDaVa ReKLaM FiRSaTi !
Iyi günler
Web sitenizin, firmanýzýn, ürünlerinizin, broþürlerinizin reklamýný tüm
türkiyeye hýzlý, düþük maliyetle, çok etkili bir þekilde yapmak
istermisiniz?
Türkiyede bulunan 7,6 milyon internet kullanicisina Reklamlarýnýzý
E-Mail yolu ile
| Akim Demaille writes:
| the following paragraph is not honored by gettextize:
|
| `aclocal.m4' at top level
| -
|
| If you do not have an `aclocal.m4' file in your distribution, the
| simplest is to concatenate the files `codeset.m4', `gettext.m4',
|
| It is correct. If gettextize did not copy these files, the subsequent
| 'aclocal' invocation would fail. I consider this a bug in the
| 'aclocal' program version 1.5.
Ah, I now understand (I think). In the ``default'' environment,
gettext macro files are installed where aclocal will find
Akim Demaille writes:
| Running gettextize on a project that is not including intl/ still
| copies and installs m4 files that are not needed.
|
| It is correct. If gettextize did not copy these files, the subsequent
| 'aclocal' invocation would fail. I consider this a bug in the
|
On Tue, Sep 03, 2002 at 11:31:49PM +0200, Alexandre Duret-Lutz wrote:
Eric == Eric Siegerman [EMAIL PROTECTED] writes:
Eric *please* consider making it an extra subdirectory
Eric level instead of a filename component, as in Josef's
Eric xx/man1/foo.1.
Yep, however the question isn't
Waldemar Rosenbach [EMAIL PROTECTED] writes:
Is there another way to solve this kind of problem?
well, it's not clean, but you can process the headers on install. this could
be a provisional approach (i.e., kludge) while you make the interface platform
independent.
see below for
Thien-Thi Nguyen [EMAIL PROTECTED] writes (imprecisely):
you can process the headers on install.
sorry, i forgot to emphasize: the headers processed are those other than
config.h -- the horrible approach described does not require you to install
config.h. (did i mention that this approach
Thien-Thi Nguyen wrote:
Thien-Thi Nguyen [EMAIL PROTECTED] writes (imprecisely):
you can process the headers on install.
sorry, i forgot to emphasize: the headers processed are those other than
config.h -- the horrible approach described does not require you to install
config.h.
Es schrieb Schleicher Ralph (LLI):
Waldemar Rosenbach [EMAIL PROTECTED] writes:
But what is the best way to deal with the platform depend stuff in the
interface?
A platform independent interface!
among the problems of ac_create_config_h:
* some ac-checks will check the compiler,
Bruce Korb [EMAIL PROTECTED] writes:
http://ac-archive.sf.net/Miscellaneous/ac_create_prefix_config_h.html
thanks for the tip. fwiw, to try this i had to substitute
AC_ECHO_MKFILE(foo,bar)
with
echo 'foo' bar
(the AC_ECHO_MKFILE from the website is empty.)
thi
Dear [EMAIL PROTECTED],
Do you know anyone who works or lives in any of these areas:
Alvechurch, Barnt Green, Blackwell, Cofton Hackett, Rednal, Lickey,
Hopwood, Marlbrook?(North Bromsgrove area UK)
Does their telephone number start either 0121-445 or 0121-447?
Please forward this email to
13 matches
Mail list logo
