<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>k-Wave User Forum &#187; Topic: Compiling source codes on Mac</title>
		<link>http://www.k-wave.org/forum/topic/compiling-source-codes-on-mac</link>
		<description>Support for the k-Wave MATLAB toolbox</description>
		<language>en-US</language>
		<pubDate>Tue, 12 May 2026 23:27:41 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.2</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.k-wave.org/forum/search.php</link>
		</textInput>
		<atom:link href="http://www.k-wave.org/forum/rss/topic/compiling-source-codes-on-mac" rel="self" type="application/rss+xml" />

		<item>
			<title>SHickling on "Compiling source codes on Mac"</title>
			<link>http://www.k-wave.org/forum/topic/compiling-source-codes-on-mac#post-4878</link>
			<pubDate>Mon, 08 Dec 2014 16:20:44 +0000</pubDate>
			<dc:creator>SHickling</dc:creator>
			<guid isPermaLink="false">4878@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Thanks so much, I'll give it a try and let you know!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Jiri Jaros on "Compiling source codes on Mac"</title>
			<link>http://www.k-wave.org/forum/topic/compiling-source-codes-on-mac#post-4877</link>
			<pubDate>Sat, 06 Dec 2014 09:33:51 +0000</pubDate>
			<dc:creator>Jiri Jaros</dc:creator>
			<guid isPermaLink="false">4877@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hi Susannah,&#60;/p&#62;
&#60;p&#62;The source codes don't support Mac OS at this moment.&#60;/p&#62;
&#60;p&#62;There are a few reasons for this:&#60;br /&#62;
1) The code would have to be rigorously tested on different versions of Mac OS that are not backwards/forward compatible - this itself could take a long time. Every single build now takes about 24 hours to validate on a high-end cluster.&#60;br /&#62;
2) I don't have a Mac to test the code on (To support different version of Mac OS, I'd need multiple computers with MacOS 10.6-10.10).&#60;br /&#62;
3) We would need additional commercial licenses of Intel compiler to create builds for Mac (one per MacOs version). The price for Intel compiler is now $1599 per computer, per year. Unfortunately, we are not allowed to distribute builds with GNU C++ and FFTW since the licenses are not compatible.&#60;/p&#62;
&#60;p&#62;However, compilation with GNU C++ and FFTW is not supposed to be so difficult. There are a few differences in memory allocation that I've already overcome I hope.&#60;/p&#62;
&#60;p&#62;What needs to be changed by you, is to go over the code and find __linux__ preprocessor directive and create a code path for __APPLE__ which may but also may not be the same. In any case, these compiler/OS specific code paths serve for getting system information (number of cpu cores, memory used, consumed time, and other reports). &#60;/p&#62;
&#60;p&#62;If this is not critical for you, I'm more than happy to lend you a helping hand to make the code running on MacOS, just send me an email.&#60;/p&#62;
&#60;p&#62;Cheers!&#60;br /&#62;
Jiri
&#60;/p&#62;</description>
		</item>
		<item>
			<title>SHickling on "Compiling source codes on Mac"</title>
			<link>http://www.k-wave.org/forum/topic/compiling-source-codes-on-mac#post-4867</link>
			<pubDate>Thu, 04 Dec 2014 22:13:14 +0000</pubDate>
			<dc:creator>SHickling</dc:creator>
			<guid isPermaLink="false">4867@http://www.k-wave.org/forum/</guid>
			<description>&#60;p&#62;Hello,&#60;/p&#62;
&#60;p&#62;I would like to compile the source codes for use on a Mac OS 10.10). I downloaded the HTF5 and FFTW libraries, but get errors when I go to make the k-Wave source code. I know this was originally written for Linux, but are there steps for how to do it on a mac?&#60;/p&#62;
&#60;p&#62;Thanks!&#60;br /&#62;
Susannah
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
