dev.ed.am
Arduino Makefile
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Arduino Makefile / Closed Bug report #4 Issues on OS X (preferences.conf, install location, avrdude.conf)
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
Go to the next issue (open or closed)
Go to the next open issue
This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Bug report
  • Targetted for
    0.5 release
  • Status
    Fixed
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    RESOLVED
  • Reproducability
    Always
  • Severity
    Not determined
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Description
Sorry for not separating the issues to different bug reports; I don't know if you'd be willing to push OS X support...

So:
# The preferences.txt file is found as ~/Library/Arduino/preferences.txt on OS X. So the current (rev.72) arduino.mk doesn't find it (so doesn't set SKETCHBOOKDIR and so the user libraries aren't found - that's how I came across this issue).
# The ARDUINODIR variable needs to point to <Location_of_Arduino.app>/Contents/Resources/Java (so not to the install location of Arduino.app) - but this is fixable in individual Makefiles, so not much problem at all. The usual locations for Arduino.app are either /Applications/Arduino.app or ~/Applications/Arduino.app (with the first one being used much more heavily) - so you could add these two into the default list.
# "make upload" does a good (correct) guess for the serial port, but avrdude complains:
avrdude: can't open config file "/usr/local/etc/avrdude.conf": No such file or directory
avrdude: error reading system wide configuration file "/usr/local/etc/avrdude.conf"
I couldn't understand why the Arduino.app-supplied one isn't chosen - the arduino.mk logic seemed to be correct, and I don't really know how to "debug" Makefiles.

Otherwise, the compilation itself went fine (except finding the libraries in the sketchbook directory, as mentioned above). Thanks for this, it's a great idea and good implementation!
Steps to reproduce this issue
-> On OS X <- (tried on Lion, but I can't see how these issues could depend on the version of OS X)

For 1), just "make" with any sketch referencing "local" libraries - the compilation will error out with something like "lcd_meter.ino:10:28: warning: phi_interfaces.h: No such file or directory" (where phi_interfaces.h is found in $SKETCHBOOKDIR/libraries/phi_interfaces/phi_interfaces.h).

For 2), setting ARDUINODIR to <Location_of_Arduino.app> will cause "make" say "*** ARDUINODIR is not set correctly; arduino software not found. Stop.", while setting it to <Location_of_Arduino.app>/Contents/Resources/Java will make "make" run fine.

For 3) "make upload" on any sketch which compiles (ie some which use only standard libraries).
Todos (0 / 0)
Issue created



To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To specify bold text put text between two stars, and for underlines put text between two underscores.
See more formatting tips in MarkdownFormatting.

URLs will be automatically transformed to links. If you want to add a title, use the link formatter: [[http://awesome.com/something An awesome link]].
See more formatting tips in WikiFormatting.

Cancel
AAah, sorry for the formatting - I guess I overlooked the "wiki-formatting" remark and the result is not what I intended. I can't edit the original report anymore...



Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

To specify bold text put text between two stars, and for underlines put text between two underscores.
See more formatting tips in MarkdownFormatting.

If you have certain text you don't want to be formatted, enclose it in <nowiki></nowiki> tags: "'''formatted''' text <nowiki>'''non-formatted''' text</nowiki>.
See more formatting tips in WikiFormatting.

Cancel
I've created an account, so you can contact me if you wish/need.



To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To specify bold text put text between two stars, and for underlines put text between two underscores.
See more formatting tips in MarkdownFormatting.

You can create a link directly to a wikipedia page by using the "WIKIPEDIA:" link namespace: "Here is a link to the wikipedia article about [[WIKIPEDIA:Norway|Norway]].
See more formatting tips in WikiFormatting.

Cancel
Hi, thanks for the detailed bug report!

xyzzy wrote:
so doesn't set SKETCHBOOKDIR and so the user libraries aren't found
I wondered if I could ask you a quick question, as I know next to nothing about Macs. I'm a bit concerned about the SKETCHBOOKDIR... Makefiles (well, make, actually) don't handle spaces in paths well, at all! Is there a "default" or commonly used location for the Arduino sketchbook directory on a Mac? And does it have any spaces in it?



Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

The Bug Genie uses an enhanced flavor of the markdown syntax, which makes each newline count. If you want to add a linebreak, add a new line and it will be presented just like you type.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in WikiFormatting.

Cancel
The issue was updated with the following change(s):
  • This issue's description has been changed
  • The status has been updated, from New to Investigating.



To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To specify bold text put text between two stars, and for underlines put text between two underscores.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in WikiFormatting.

Cancel
The issue was updated with the following change(s):
  • The issue's poster has been changed, from Guest user to xyzzy.



Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in MarkdownFormatting.

URLs will be automatically transformed to links. If you want to add a title, use the link formatter: [[http://awesome.com/something An awesome link]].
See more formatting tips in WikiFormatting.

Cancel
The issue was updated with the following change(s):
  • The status has been updated, from Investigating to Being worked on.



Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples in <source></source> tags.
See more formatting tips in WikiFormatting.

Cancel
The issue was updated with the following change(s):
  • The milestone has been updated, from Not determined to 0.5 release.



To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

To specify bold text put text between two stars, and for underlines put text between two underscores.
See more formatting tips in MarkdownFormatting.

If you want to add text that is not supposed to be parsed, put it inside <nowiki> tags, or start the line with a space.
See more formatting tips in WikiFormatting.

Cancel
Great! Thanks!

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Being worked on to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.



To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

The Bug Genie uses an enhanced flavor of the markdown syntax, which makes each newline count. If you want to add a linebreak, add a new line and it will be presented just like you type.
See more formatting tips in MarkdownFormatting.

The Bug Genie will automatically add new lines when you add two new lines in your text, whereas one new line is used for formatting as you type. To force a new line, use the <br> tag: "There is a new<br>line here".
See more formatting tips in WikiFormatting.

Cancel
The issue was updated with the following change(s):
  • The status has been updated, from Closed to New.
  • This issue has been reopened
  • The resolution has been updated, from RESOLVED to Not determined.
  • This issue's progression has been updated to 0 percent completed.



Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in MarkdownFormatting.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples in <source></source> tags.
See more formatting tips in WikiFormatting.

Cancel
The issue was updated with the following change(s):
  • The status has been updated, from New to Fixed.



To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

If you want to add text that is not supposed to be parsed, put it inside <nowiki> tags, or start the line with a space.
See more formatting tips in WikiFormatting.

Cancel
The issue was updated with the following change(s):
  • This issue has been closed
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
footer_logo.png The Bug Genie 4.3.1 | Support | Feedback spinning_16.gif