unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: eactors@aol.com
To: 14672@debbugs.gnu.org
Subject: bug#14672: QT port for ARM within guile
Date: Thu, 20 Jun 2013 03:07:14 -0400 (EDT)	[thread overview]
Message-ID: <8D03B9BED2EFC3E-1390-337FC@webmail-vd011.sysops.aol.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]



Hello,
I founda quick thread implementation for ARM within the guile svn: (http://git.savannah.gnu.org/gitweb/?p=guile.git;a=tree;f=qt;h=c98346f9299df235964738dbf4b87da9806c9f52;hb=72e4a3b1df86fdfca752221716c3e3f5573ff6a5


Hope you can help me with this. Do youknow what the status of this port was? Did it work? I would like to add a QTfor ARM into the SystemC Open Source Project and I’m looking for a goodstarting point.
 
ManyThanks in advance 
eactor
 



[-- Attachment #2: Type: text/html, Size: 2135 bytes --]

             reply	other threads:[~2013-06-20  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20  7:07 eactors [this message]
2013-06-20 21:24 ` bug#14672: QT port for ARM within guile Noah Lavine
2013-06-21  6:13   ` eactors
2013-06-21 13:42     ` Noah Lavine
2013-06-21 21:29 ` Mark H Weaver

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8D03B9BED2EFC3E-1390-337FC@webmail-vd011.sysops.aol.com \
    --to=eactors@aol.com \
    --cc=14672@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).