public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: swami91 <to.swami@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Standalone application - expanding export functions
Date: Fri, 13 Jun 2014 12:28:08 -0700 (PDT)	[thread overview]
Message-ID: <1402687688522-182313.post@n7.nabble.com> (raw)

Hi,


  I was going through the document in doc/README.standalone. It says I can
add addition functions to export/_export.h:

"   To export some additional function foobar(), the following steps             
   should be undertaken:                                                         
   - Append the following line at the end of the include/_exports.h             
     file:                                                                         
        EXPORT_FUNC(foobar)   "      
    
But the discussion in the following thread by Wolfgang says the standalone
function will have to be GPLed if expanded. 
                                                                        
 
http://u-boot.10912.n7.nabble.com/Using-U-Boot-in-a-mixed-licensed-environment-td142874.html

I am confused. Can you please clarify if we can expand the export functions
with both with u-boot code functions and the functions I add to u-boot and
still not to GPL the standalone application if it uses those functions?

Thanks,
-Sudhakar




--
View this message in context: http://u-boot.10912.n7.nabble.com/Standalone-application-expanding-export-functions-tp182313.html
Sent from the U-Boot mailing list archive at Nabble.com.

             reply	other threads:[~2014-06-13 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 19:28 swami91 [this message]
2014-06-13 21:40 ` [U-Boot] Standalone application - expanding export functions Wolfgang Denk
2014-06-14  2:01 ` swami91
2014-06-14  4:58   ` Wolfgang Denk

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

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

  git send-email \
    --in-reply-to=1402687688522-182313.post@n7.nabble.com \
    --to=to.swami@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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