Comments (8)
The issue is that while you have added utility to the include path, no c files from that subdirectory are being compiled.
Change the LCPP_FILES definition to this
LCPP_FILES := $(wildcard $(LIBRARYPATH)/*/*.cpp) $(wildcard $(LIBRARYPATH)/SD/utility/*.cpp)
A better solution would be to make LC_FILES recurse directories, but there isn't an easy way to do that without using $(shell find ...)
to my knowledge, which isnt the most portable
from teensy-template.
Ah yes, of course. Thanks!
LC_FILES := $(wildcard $(LIBRARYPATH)/*/*.c) $(wildcard $(LIBRARYPATH)/*/utility/*.c)
LCPP_FILES := $(wildcard $(LIBRARYPATH)/*/*.cpp) $(wildcard $(LIBRARYPATH)/*/utility/*.cpp)
A better solution would be to make LC_FILES recurse directories, but there isn't an easy way to do that without using $(shell find ...) to my knowledge, which isnt the most portable
Says the person that has the words "What is Win Dose?" in their makefile and put compiled binaries into their git repository ;)
from teensy-template.
Touche. You just gave me a good laugh. It's been so long since I looked at
this project I forgot its targeted at nix specifically.
On Nov 21, 2014 6:24 AM, "Kaspar Emanuel" [email protected] wrote:
Ah yes, of course. Thanks!
LC_FILES :=
$(wildcard $ (LIBRARYPATH)//.c)$(wildcard $ (LIBRARYPATH)//utility/.c)
LCPP_FILES :=$(wildcard $ (LIBRARYPATH)//.cpp)$(wildcard $ (LIBRARYPATH)//utility/.cpp)A better solution would be to make LC_FILES recurse directories, but
there isn't an easy way to do that without using $(shell find ...) to my
knowledge, which isnt the most portableSays the person that has the words "What is Win Dose?" in their makefile
and put compiled binaries into their git repository ;)—
Reply to this email directly or view it on GitHub
#7 (comment)
.
from teensy-template.
You point is valid though. Detecting windows and removing the binaries is more easily fixable. Recursing might be harder.
from teensy-template.
To be fair, I doubt a Windows user would hardly appreciate us removing all
their binaries from system32 instead of adding Windows support ;)
On Nov 21, 2014 6:32 AM, "Kaspar Emanuel" [email protected] wrote:
You point is valid though. Detecting windows and removing the binaries is
more easily fixable. Recursing might be harder.—
Reply to this email directly or view it on GitHub
#7 (comment)
.
from teensy-template.
:) Jokes aside it might be nice to point at the default Arduino location on Windows like on OSX.
I'll send a pull-request with these minor fixes anyway. The */utility/*
wildcards fix the Audio library as well so I think it's worth doing.
Hopefully this means I can leave the Arduino IDE closed for another few months until I try the next Arduino compatible board.
from teensy-template.
How many of the included arduino libraries use sub directories? My guess is
very few. A hacky solution is to just duplicate the wildcard there with
another subdirectory level.
//*.c basically.
Should cover any/all libraries. I can't imagine any use more than one
subdirectory.
On Nov 21, 2014 6:40 AM, "Kaspar Emanuel" [email protected] wrote:
:) Jokes aside it might be nice to point at the default Arduino location
on Windows like on OSX.I'll send a pull-request with these minor fixes anyway. The /utility/
wildcards fix the Audio library as well so I think it's worth doing.Hopefully this means I can leave the Arduino IDE closed for another few
months until I try the next Arduino compatible board.—
Reply to this email directly or view it on GitHub
#7 (comment)
.
from teensy-template.
Hmm yeah, */*/*.c
is better. My thought was we don't want to compile the examples
dir source files but those are normally two directories deep anyway.
I want to get rid of the binaries, they don't work on my (32-bit) Ubuntu either. It might actually be worth clearing the history of them because it really slows down git. You'd have to do that though (delete repo, create new one with the same name and then rm -rf .git && git init && git add .
and commit and push that).
from teensy-template.
Related Issues (13)
- Teensy 3.1 update? HOT 4
- Does this support Teensy 3.2? HOT 2
- LDFlags
- Binaries in tools folder may be out of date
- Remove GCC toolchain HOT 2
- Missing license HOT 2
- Make not working after clone on OSX HOT 1
- Teensy 4 HOT 1
- Problem with dependencies
- Issues while porting arduino code HOT 5
- Add support for OSX HOT 2
- Request: Teensy LC Support HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from teensy-template.