public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
* re-split all frysk-import's CNI code into frysk-sys
@ 2007-07-12 13:57 Andrew Cagney
  2007-07-17 18:36 ` Andrew Cagney
  0 siblings, 1 reply; 2+ messages in thread
From: Andrew Cagney @ 2007-07-12 13:57 UTC (permalink / raw)
  To: frysk

I'm going to investigate moving all of the cni (bindings) code in 
frysk-imports moving it into frysk-sys.  That would be the lib/ frysk/ 
and inua/ directories.

At present working on those bindings is a pta as it is too easy to 
trigger an unnecessary re-build / re-conf when modifying a binding.  
This will also open the way for making parts of frysk-imports, such 
libunwind and elfutils optional.

http://sourceware.org/bugzilla/show_bug.cgi?id=4784

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: re-split all frysk-import's CNI code into frysk-sys
  2007-07-12 13:57 re-split all frysk-import's CNI code into frysk-sys Andrew Cagney
@ 2007-07-17 18:36 ` Andrew Cagney
  0 siblings, 0 replies; 2+ messages in thread
From: Andrew Cagney @ 2007-07-17 18:36 UTC (permalink / raw)
  To: frysk

(after a false start) I've checked this in; take care.

Andrew Cagney wrote:
> I'm going to investigate moving all of the cni (bindings) code in 
> frysk-imports moving it into frysk-sys.  That would be the lib/ frysk/ 
> and inua/ directories.
>
> At present working on those bindings is a pta as it is too easy to 
> trigger an unnecessary re-build / re-conf when modifying a binding.  
> This will also open the way for making parts of frysk-imports, such 
> libunwind and elfutils optional.
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=4784

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-07-17 18:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-12 13:57 re-split all frysk-import's CNI code into frysk-sys Andrew Cagney
2007-07-17 18:36 ` Andrew Cagney

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).