logo       

New package esnacc: msg#00119

t2.devel

Subject: New package esnacc


This is a multi-part message in MIME format. Hi,

I tried my hand at another new package for T2.

Esnacc is a compiler that can create C and C++ code for reading and writing BER-encoded structures specified in ASN.1.

I ran into two problems where I do not know what the proper T2-way of fixing them would be.

1) Incorporate upstream patches

The distribution consists of a tarball with the code for version 1.7 and two separate tarballs updating that to version 1.7.3 and then to 1.7.4. These
tarballs contain files that replace the older ones.

For now I have made the patch-tars part of the T2-package and written a prepatch-hook that unpacks them.

No doubt it would be much better to download them from the upstream sources
just like the 1.7 tarball and unpack from the download-directory. Can that
be done?

2) Conditional patching?

I am cross-compiling and the distribution includes examples that try to run
code that has just been cross-built. Failing miserably. I could not find
configure-options to disable these examples and thus have created a patch
that just removes them from the SUBDIRS traversed during the build.

That of course means, that no one will get any examples compiled for them,
even if it were possible.

Is there a better way? To only apply the patch when cross-compiling?

3) Custom install-sh

The package comes with it's own version of install-sh. Thus install is not
wrapped. Thus the files go outside of the build-directory and that's it.

I have tried several approaches modifying confopt and makeinstopt but I
failed.

Ciao, MM
--
Marian Aldenhövel, Rosenhain 23, 53123 Bonn
http://www.marian-aldenhoevel.de
"I ran some quick calculations on it. He's about 80% on the right
track. That leaves him only 20% dead when he crashes." Bob C

Attachment: esnacc.zip
Description: Zip compressed data



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise