Succeeded in building on OSX 10.8

Discussions related to embedded firmware, driver, and user mode application software development

Moderator: robert.ghilduta

Post Reply
edy555
Posts: 4
Joined: Sat Mar 02, 2013 3:11 am

Succeeded in building on OSX 10.8

Post by edy555 » Mon Sep 02, 2013 9:02 am

Hi all,
I tried to build up bladeRF-cli and gr-osmosdr on Mac OSX (10.8), and had success in working good.
See details in following link. (because original article is written in Japanese, so this link is to google-translate.)
http://translate.google.com/translate?s ... 075813222/
---
@edy555

tfm55x
Posts: 5
Joined: Sat Aug 03, 2013 5:15 pm

Re: Succeeded in building on OSX 10.8

Post by tfm55x » Wed Sep 04, 2013 1:11 pm

Thanks for figuring this out! I'm looking forward to using my new BladeRF natively on my MacBook!

tfm55x
Posts: 5
Joined: Sat Aug 03, 2013 5:15 pm

Re: Succeeded in building on OSX 10.8

Post by tfm55x » Wed Sep 04, 2013 4:26 pm

By any chance, did you encounter any problem when issuing the 'cmake -DINSTALL_UDEV_RULES=OFF ..' command while building the bladeRF package?

I'm seeing the following warning, even though I successfully installed libUSB via brew. I added a '-DLIBUSB_PATH=/usr/local/lib' directive, but that didn't affect the problem.

CMake Error at cmake/modules/FindLibUSB.cmake:120 (message):
libusb-1.0 not found - is it installed? If you're using a binary
distribution, try setting -DLIBUSB_PATH=<path_to_libusb_files>.

bpadalino
Posts: 303
Joined: Mon Mar 04, 2013 4:53 pm

Re: Succeeded in building on OSX 10.8

Post by bpadalino » Wed Sep 04, 2013 5:11 pm

That is interesting. When I build on my system, which uses macports instead of homebrew, pkg-config picked up libusb. Does homebrew use pkg-config at all, or is there a way to tell pkg-config about libusb being there? It definitely should find the library if it's in /usr/local/lib. Have you verified that there is a libusb-1.0.dylib there? What if you just pass in /usr/local instead of /usr/local/lib?

edy555
Posts: 4
Joined: Sat Mar 02, 2013 3:11 am

Re: Succeeded in building on OSX 10.8

Post by edy555 » Thu Sep 05, 2013 4:07 am

tfm55x wrote:By any chance, did you encounter any problem when issuing the 'cmake -DINSTALL_UDEV_RULES=OFF ..' command while building the bladeRF package?
I did not encounter any warnings at all.
In my system with homebrew, pkg-config shows as follows, and there is symbolic link in /usr/local/lib.

$ pkg-config libusb-1.0 --libs
-L/usr/local/Cellar/libusb/1.0.9/lib -lusb-1.0
$ ls -l /usr/local/lib/libusb-1.0.dylib
lrwxr-xr-x 1 user wheel 43 Aug 24 18:59 /usr/local/lib/libusb-1.0.dylib -> ../Cellar/libusb/1.0.9/lib/libusb-1.0.dylib

Are there any differences from your system?

djrevmoon
Posts: 30
Joined: Fri Mar 01, 2013 4:37 am

Re: Succeeded in building on OSX 10.8

Post by djrevmoon » Fri Sep 06, 2013 9:27 am

I have the same issues compiling on Mac OSX so I also checked the pkg-config:

$pkg-config libusb-1.0 --libs
-L/usr/local/Cellar/libusb/1.0.9/lib -lusb-1.0
$ ls -l /usr/local/lib/libusb-1.0.dylib
lrwxr-xr-x 1 me admin 43 4 Sep 13:25 /usr/local/lib/libusb-1.0.dylib -> ../Cellar/libusb/1.0.9/lib/libusb-1.0.dylib

but nevertheless the build fails on not finding libusb-1.0

edy555
Posts: 4
Joined: Sat Mar 02, 2013 3:11 am

Re: Succeeded in building on OSX 10.8

Post by edy555 » Fri Sep 06, 2013 11:37 pm

Hmm.. For reference, this is output from cmake in success.
$ cmake -DINSTALL_UDEV_RULES=OFF ..
-- The C compiler identification is Clang 4.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Build type not specified: defaulting to a release build.
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.28")
-- checking for module 'libusb-1.0'
-- found libusb-1.0, version 1.0.9
-- Looking for libusb_get_device_list in /usr/local/lib/libusb-1.0.dylib
-- Looking for libusb_get_device_list in /usr/local/lib/libusb-1.0.dylib - found
-- In libraries /Users/user/Projects/bladerf/host/common/src
-- libbladeRF version: 0.3.0-git-9e0be95-dirty
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- nuand bladeRF udev rules will not be installed because INSTALL_UDEV_RULES=OFF
-- checking for module 'libtecla'
-- package 'libtecla' not found
-- Found libtecla: /usr/local/include, /usr/local/lib/libtecla.dylib
-- libtecla support enabled
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Configured to build bladeRF-cli version: 0.4.0-git-9e0be95-dirty
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/user/Projects/bladerf/host/build
file command output about libusb-1.0.dylib.
$ file /usr/local/lib/libusb-1.0.dylib
/usr/local/lib/libusb-1.0.dylib: Mach-O 64-bit dynamically linked shared library x86_64

Vine
Posts: 18
Joined: Sat Jun 15, 2013 6:04 am

Re: Succeeded in building on OSX 10.8

Post by Vine » Sat Sep 14, 2013 3:15 am

Hi,

Did you have any problem with "orc" dependency when installing gnuradio ? That's what I have :

Code: Select all

==> Downloading http://code.entropywave.com/download/orc/orc-0.4.17.tar.gz
Already downloaded: /Library/Caches/Homebrew/orc-0.4.17.tar.gz
Error: SHA1 mismatch
Expected: 5cb7b3225a23bc4a5771a62e9c94a90d21609632
Actual: b2213ef721d1ce333eb5fc3e1906215c5b6ed077
Archive: /Library/Caches/Homebrew/orc-0.4.17.tar.gz
(To retry an incomplete download, remove the file above.)
I've tried to remove /Library/Caches/Homebrew/orc-0.4.17.tar.gz but it still fail.

Vincent

Montezuma
Posts: 35
Joined: Fri Mar 01, 2013 6:42 am

Re: Succeeded in building on OSX 10.8

Post by Montezuma » Mon Sep 16, 2013 9:18 pm

edy555 wrote:Hi all,
I tried to build up bladeRF-cli and gr-osmosdr on Mac OSX (10.8), and had success in working good.
See details in following link. (because original article is written in Japanese, so this link is to google-translate.)
http://translate.google.com/translate?s ... 075813222/
---
@edy555
Just as a suggestion to all bladeRF owners, and any owners of transceiver equipment of any kind, it is best to only power on RF equipment with antennas attached. Otherwise, this seems as if it was a good find.

Post Reply