public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: ISO boost library help
Date: Tue, 24 Oct 2017 17:25:00 -0000	[thread overview]
Message-ID: <BN6PR2001MB1074DB8A47EA988B19B06F5CF1470@BN6PR2001MB1074.namprd20.prod.outlook.com> (raw)

Trying unsuccessfully (so far) to use the Cygwin-provided boost libraries. The 
only boost-related package I saw was boost-build, which I've installed.

$ cygcheck -c boost-build
Cygwin Package Information
Package              Version        Status
boost-build          1.63.0-1       OK
$

Google seems to be telling me that I have to build (compile) the libraries with 
bjam, but finding no relevant documentation on how to do that from the Cygwin 
package.

$ pwd
/usr/share/boost-build
$ ls -l
total 5
-rw-r--r--  1 knellis Domain Users 267 May 19 04:44 boost-build.jam
drwxr-xr-x+ 1 knellis Domain Users   0 Oct 24 12:01 example
drwxr-xr-x+ 1 knellis Domain Users   0 Oct 24 12:01 src
$ bjam
warning: No toolsets are configured.
warning: Configuring default toolset "gcc".
warning: If the default is wrong, your build may not work correctly.
warning: Use the "toolset=xxxxx" option to override our guess.
warning: For more configuration options, please consult
warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
error: no Jamfile in current directory found, and no target references specified.

$

Would appreciate some pointers.

--Ken Nellis

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2017-10-24 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 17:25 Nellis, Kenneth [this message]
2017-10-24 17:32 ` Marco Atzeri
2017-10-24 18:23   ` Nellis, Kenneth
2017-10-24 19:10 ` Csaba Raduly

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=BN6PR2001MB1074DB8A47EA988B19B06F5CF1470@BN6PR2001MB1074.namprd20.prod.outlook.com \
    --to=kenneth.nellis@conduent.com \
    --cc=cygwin@cygwin.com \
    /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).