-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSX: How to reference boost library #794
Comments
|
Aloha.
I use macports. Can't install brew with it.
J.
…On 5/28/24 15:24, 0tkl wrote:
|brew install boost|
—
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136351521__;Iw!!Mih3wA!Dm-TeJiFSkIXIHb5XxsjY4XF3iCrVwv4tDCvgrV5GDHYr5hsRVxTwfEiPumgO4uKNaCLWswH5RIRB5qLqsS64sbl$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQAY526JKDGN26F76JLZEUU6VAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGM2TCNJSGE__;!!Mih3wA!Dm-TeJiFSkIXIHb5XxsjY4XF3iCrVwv4tDCvgrV5GDHYr5hsRVxTwfEiPumgO4uKNaCLWswH5RIRB5qLql-mPRzO$>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
--------------5Df1SK1JWbihRosZaQwxtVg3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Aloha.<br>
<br>
I use macports. Can't install brew with it.<br>
<br>
J.<br>
<br>
<div class="moz-cite-prefix">On 5/28/24 15:24, 0tkl wrote:<br>
</div>
<blockquote type="cite" ***@***.***">
<p dir="auto"><code class="notranslate">brew install boost</code></p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
Reply to this email directly, <a href="https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136351521__;Iw!!Mih3wA!Dm-TeJiFSkIXIHb5XxsjY4XF3iCrVwv4tDCvgrV5GDHYr5hsRVxTwfEiPumgO4uKNaCLWswH5RIRB5qLqsS64sbl$" moz-do-not-send="true">view it on GitHub</a>, or <a href="https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQAY526JKDGN26F76JLZEUU6VAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGM2TCNJSGE__;!!Mih3wA!Dm-TeJiFSkIXIHb5XxsjY4XF3iCrVwv4tDCvgrV5GDHYr5hsRVxTwfEiPumgO4uKNaCLWswH5RIRB5qLql-mPRzO$" moz-do-not-send="true">unsubscribe</a>.<br>
You are receiving this because you authored the thread.<img src="https://github.com/notifications/beacon/AZ3YXQBMYBBRYRICTHSCMILZEUU6VA5CNFSM6AAAAABIIGNSZGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT7KYRSC.gif" alt="" moz-do-not-send="true" width="1" height="1"><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message
ID: <span><OpenWaterAnalytics/EPANET/issues/794/2136351521</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#794 (comment)",
"url": "#794 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
<a class="moz-txt-link-freetext" href="https://www.sdsc.edu/~hellyj">https://www.sdsc.edu/~hellyj</a> / 808 205 9882 / 760 8408660</pre>
</body>
</html>
--------------5Df1SK1JWbihRosZaQwxtVg3--
|
Does |
Yes. That's does it. I have a similar problem with swmm5. Do you have
any idea how to fix these library paths so they don't have to be in the
command-line? I mean is there some way to properly reference the PATHs
so there is no need for a command-line modifier or shell wrapper?
J.
…On 5/28/24 16:28, 0tkl wrote:
LD_LIBRARY_PATH=/usr/local/boost_1_85_0:$LD_LIBRARY_PATH cmake
--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
|
Another way to think of this is 'Where does brew put it'?
J.
…On 5/28/24 16:28, 0tkl wrote:
Does |LD_LIBRARY_PATH=/usr/local/boost_1_85_0:$LD_LIBRARY_PATH cmake
<arguments>| work?
—
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136403761__;Iw!!Mih3wA!Dg2qn7hrbHuXT7q9UGBjlmo-kxWx21v8p7Tc7xp89K2elx8V9hW4xpSuwRl1JGxzQDPmWBkeWGWWYJfepfrTeG3g$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQBOCP527ZTJQWIETI3ZEU4LBAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGQYDGNZWGE__;!!Mih3wA!Dg2qn7hrbHuXT7q9UGBjlmo-kxWx21v8p7Tc7xp89K2elx8V9hW4xpSuwRl1JGxzQDPmWBkeWGWWYJfepRVXT9_P$>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
--------------QL0P3AH2GYEzomYxxUwP0YAv
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Another way to think of this is 'Where does brew put it'?<br>
<br>
J.<br>
<br>
<div class="moz-cite-prefix">On 5/28/24 16:28, 0tkl wrote:<br>
</div>
<blockquote type="cite" ***@***.***">
<p dir="auto">Does <code class="notranslate">LD_LIBRARY_PATH=/usr/local/boost_1_85_0:$LD_LIBRARY_PATH
cmake <arguments></code> work?</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
Reply to this email directly, <a href="https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136403761__;Iw!!Mih3wA!Dg2qn7hrbHuXT7q9UGBjlmo-kxWx21v8p7Tc7xp89K2elx8V9hW4xpSuwRl1JGxzQDPmWBkeWGWWYJfepfrTeG3g$" moz-do-not-send="true">view it on GitHub</a>, or <a href="https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQBOCP527ZTJQWIETI3ZEU4LBAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGQYDGNZWGE__;!!Mih3wA!Dg2qn7hrbHuXT7q9UGBjlmo-kxWx21v8p7Tc7xp89K2elx8V9hW4xpSuwRl1JGxzQDPmWBkeWGWWYJfepRVXT9_P$" moz-do-not-send="true">unsubscribe</a>.<br>
You are receiving this because you authored the thread.<img src="https://github.com/notifications/beacon/AZ3YXQF2OLGQBEK3QMLL3YLZEU4LBA5CNFSM6AAAAABIIGNSZGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT7K3XTC.gif" alt="" moz-do-not-send="true" width="1" height="1"><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message
ID: <span><OpenWaterAnalytics/EPANET/issues/794/2136403761</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#794 (comment)",
"url": "#794 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
<a class="moz-txt-link-freetext" href="https://www.sdsc.edu/~hellyj">https://www.sdsc.edu/~hellyj</a> / 808 205 9882 / 760 8408660</pre>
</body>
</html>
--------------QL0P3AH2GYEzomYxxUwP0YAv--
|
You do realize that the unit tests and regression tests are run whenever you submit a pull request. Personally I've never bothered to install Boost and build the unit test executables locally. Instead I work with a fork of the repo, make my code changes on it, submit a PR for them and then review the Appveyor report of the test results. |
Aloha.
I don't understand the import of your message. I am running on OSX and
am attempting to learn EPANET and assumed the tests would be
illuminating as to how to use it. Sounds like the tests are irrelevant
to a user. Is that your point?
J.
…On 5/28/24 18:18, Lew Rossman wrote:
You do realize that the unit tests and regression tests are run
whenever you submit a pull request. Personally I've never bothered to
install Boost and build the unit test executables locally. Instead I
work with a fork of the repo, make my code changes on it, submit a PR
for them and then review the Appveyor report of the test results.
—
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136482957__;Iw!!Mih3wA!G9xo3JrFLe8eiGcp-U1fu8R8xW4XyK9yf3so_OqJDlmCAQOgjjXgTsZ6gRNQ4GIqbMbaHDo2kg9liIMu-CgrsT5I$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQBCRTOXIB6G4RBBV5LZEVJLBAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGQ4DEOJVG4__;!!Mih3wA!G9xo3JrFLe8eiGcp-U1fu8R8xW4XyK9yf3so_OqJDlmCAQOgjjXgTsZ6gRNQ4GIqbMbaHDo2kg9liIMu-NLsY21R$>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
--------------100zXhC1zK3ZPQOvUE1ceE8S
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Aloha.<br>
<br>
I don't understand the import of your message. I am running on OSX
and am attempting to learn EPANET and assumed the tests would be
illuminating as to how to use it. Sounds like the tests are
irrelevant to a user. Is that your point?<br>
<br>
J.<br>
<br>
<div class="moz-cite-prefix">On 5/28/24 18:18, Lew Rossman wrote:<br>
</div>
<blockquote type="cite" ***@***.***">
<p dir="auto">You do realize that the unit tests and regression
tests are run whenever you submit a pull request. Personally
I've never bothered to install Boost and build the unit test
executables locally. Instead I work with a fork of the repo,
make my code changes on it, submit a PR for them and then review
the Appveyor report of the test results.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
Reply to this email directly, <a href="https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136482957__;Iw!!Mih3wA!G9xo3JrFLe8eiGcp-U1fu8R8xW4XyK9yf3so_OqJDlmCAQOgjjXgTsZ6gRNQ4GIqbMbaHDo2kg9liIMu-CgrsT5I$" moz-do-not-send="true">view it on GitHub</a>, or <a href="https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQBCRTOXIB6G4RBBV5LZEVJLBAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGQ4DEOJVG4__;!!Mih3wA!G9xo3JrFLe8eiGcp-U1fu8R8xW4XyK9yf3so_OqJDlmCAQOgjjXgTsZ6gRNQ4GIqbMbaHDo2kg9liIMu-NLsY21R$" moz-do-not-send="true">unsubscribe</a>.<br>
You are receiving this because you authored the thread.<img src="https://github.com/notifications/beacon/AZ3YXQHLAVBTPR6UMO2OUJLZEVJLBA5CNFSM6AAAAABIIGNSZGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT7LASI2.gif" alt="" moz-do-not-send="true" width="1" height="1"><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message
ID: <span><OpenWaterAnalytics/EPANET/issues/794/2136482957</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#794 (comment)",
"url": "#794 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
<a class="moz-txt-link-freetext" href="https://www.sdsc.edu/~hellyj">https://www.sdsc.edu/~hellyj</a> / 808 205 9882 / 760 8408660</pre>
</body>
</html>
--------------100zXhC1zK3ZPQOvUE1ceE8S--
|
I'd say the tests are more important for developers than for users since they are so artificial in nature (they just check that the various API functions do what they are supposed to do). If you want to learn how to use the API then you should read its documentation. It includes several more useful examples than the unit tests. If you want to learn more in general about EPANET then you should read the US EPA's User Manual. |
Reading's fine. Learning from examples, better.
J.
…On 5/28/24 19:40, Lew Rossman wrote:
I'd say the tests are more important for developers than for users
since they are so artificial in nature (they just check that the
various API functions do what they are supposed to do).
If you want to learn how to use the API then you should read its
documentation
<https://urldefense.com/v3/__http://wateranalytics.org/EPANET/__;!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5syw9rcjwv$>.
It includes several more useful examples than the unit tests. If you
want to learn more in general about EPANET then you should read the US
EPA's User Manual
<https://urldefense.com/v3/__https://epanet22.readthedocs.io/en/latest/__;!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5sy2Tjt3EY$>.
—
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136552544__;Iw!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5sy1AasTwJ$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQDGGRXLTXEDYUCC7GLZEVS4XAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGU2TENJUGQ__;!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5sy63yeJ7z$>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
--------------Mso33eEy0J9xZGjsBW20VwKT
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Reading's fine. Learning from examples, better. <br>
J.<br>
<br>
<div class="moz-cite-prefix">On 5/28/24 19:40, Lew Rossman wrote:<br>
</div>
<blockquote type="cite" ***@***.***">
<p dir="auto">I'd say the tests are more important for developers
than for users since they are so artificial in nature (they just
check that the various API functions do what they are supposed
to do).</p>
<p dir="auto">If you want to learn how to use the API then you
should read its <a href="https://urldefense.com/v3/__http://wateranalytics.org/EPANET/__;!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5syw9rcjwv$" rel="nofollow" moz-do-not-send="true">documentation</a>. It
includes several more useful examples than the unit tests. If
you want to learn more in general about EPANET then you should
read the US EPA's <a href="https://urldefense.com/v3/__https://epanet22.readthedocs.io/en/latest/__;!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5sy2Tjt3EY$" rel="nofollow" moz-do-not-send="true">User Manual</a>.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>
Reply to this email directly, <a href="https://urldefense.com/v3/__https://github.com/OpenWaterAnalytics/EPANET/issues/794*issuecomment-2136552544__;Iw!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5sy1AasTwJ$" moz-do-not-send="true">view it on GitHub</a>, or <a href="https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZ3YXQDGGRXLTXEDYUCC7GLZEVS4XAVCNFSM6AAAAABIIGNSZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWGU2TENJUGQ__;!!Mih3wA!DRNwyk5zxKkP_KSCx-xnXNDB_PhhRMKPKdReajgiP3_UF_XzZ2o3bq-1ZfBJvh7xPzd1mdOvm_S2JW5sy63yeJ7z$" moz-do-not-send="true">unsubscribe</a>.<br>
You are receiving this because you authored the thread.<img src="https://github.com/notifications/beacon/AZ3YXQAVGJDMOU44VCQGTU3ZEVS4XA5CNFSM6AAAAABIIGNSZGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT7LE2GA.gif" alt="" moz-do-not-send="true" width="1" height="1"><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message
ID: <span><OpenWaterAnalytics/EPANET/issues/794/2136552544</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#794 (comment)",
"url": "#794 (comment)",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
<a class="moz-txt-link-freetext" href="https://www.sdsc.edu/~hellyj">https://www.sdsc.edu/~hellyj</a> / 808 205 9882 / 760 8408660</pre>
</body>
</html>
--------------Mso33eEy0J9xZGjsBW20VwKT--
|
Aloha.
I've been stumbling around trying to find out how to build the 'tests'. I've installed boost (apparently) in /usr/local/boost_1_85_0 but can't quite grok how to get cmake to notice it.
Any advice would be welcome.
J
The text was updated successfully, but these errors were encountered: