Unix like time lib - by Swfltek

Go To Last Post
8 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Someone "mikericetga" just left a nice Unix like time" addon here.
It's not 100% Unix compatible , as this package has "Epoch" as Y2k Time not Jan 01 1970.

So one can't exchange seconds with a Unix system , wo. adding/subtracting the 30years.

Swfltek AVR Time
http://8515.avrfreaks.net/index....

Do read the Copyright.
Seems like it's unusable for integrating into avr-libc.
And im 99% sure i won't shuffle around that pdf , when releasing a "binary".

A pity it seemed like a nice package :?

Well it has a neat makefile 8)

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I can't see where the license requires you to re-distribute the PDF when releasing a "binary", Bingo. What am I missing (or you mis-reading)?

The "ephemera" funstions sure looks interesting. Think of all those solar-tracker threads we've had.. :D

I'll prolly take these functions for a test-ride.

Other time-code-posts:
https://www.avrfreaks.net/index.p...

https://www.avrfreaks.net/index.p...

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

License terms are the same as that of avr-libc.

It is not required, nor would it make any sense, to distribute the documentation pdf with a binary, just as it is not required to distribute the avr-libc documentation with a binary.

UNIX_OFFSET and NTP_OFFSET are defined, allowing easy translation...

time_t swfltek_timestamp = unix_timestamp - UNIX_OFFSET;

Perhaps I should make that more clear in the documentation.

Calling this a 'library' is to use the term loosely, as its really just a supplement to avr-libc, though with some Makefile changes it could become a stand alone library.

As for that Makefile, I am not a 'make master', so getting it to work on Windows and UNIXy systems was... interesting.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

as its really just a supplement to avr-libc,

Have you submitted it via the Bugzilla?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

> as its really just a supplement to avr-libc

Would you be willing to join the avr-libc team, and maintain it inside
avr-libc yourself?

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Jörg,

I would be willing to, though it would take me a while to get started, I'm sure.

I haven't submitted it to any repository yet.

Frankly, this is version 1.0, and I am looking for more critical feedback before I take things further. And what better place to be criticized, than on this forum! :)

I have beta tested with several folks, but they are mostly Arduino users, so the number of different MCUs is limited... atmega 328, 1280, 1284 and 2560.

While theoretically it should work with any architecture (and MCU with enough FLASH and RAM), you are probably familiar with the disconnect between theory and reality!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

> I would be willing to, though it would take me a while to get started, I'm sure.

OK, fine. Please get an account on savannah.nongnu.org, and then send a formal
request to join the project.

From a first glance, I don't think you're that far off. Changes I think
would be needed:

  • add copyright notice and $Id$ on top of each file
  • add documentation as doxygen comments on top of each function; since you've already got a good documentation, that's mostly copy&paste
  • add autoconf Makefile stuff, should be pretty straightforward

> I am looking for more critical feedback before I take things further.

Since it's an add-on which nobody is forced into using it (without requesting any
of its symbols, it's just going to sit in the library without interfering with
anyone else), I think it's safe to distribute it as part of avr-libc even in
version 1.0. That's probably the best way to extend its userbase.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:
I can't see where the license requires you to re-distribute the PDF when releasing a "binary", Bingo. What am I missing (or you mis-reading)?

Apparently i was misreading (since the OP) said the licence was the same as in avr-libc.

I read in the "PDF" that "every binary release should contain this copyright" , and i thought it was the PDF that was meant.

Sorry for that :oops:

/Bingo