|
Guess I get to learn how to make a nuget package then, but can they actually set up some binaries in the *source* (not bin) directory without adding them as a reference to any projects? that's what I'd need.
Sorry i know very little about them, except including them in my projects. Thus far i haven't had a need to build them until now maybe.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Absolutely no idea!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I think I'll skip that route for now. I may go with #2 though. It seems people in general aren't keen on including the binaries. I'll add a section on setting up the pre build step in the article, and reference the article for Rolex, the tool i use to generate the tokenizer.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Binaries are a problem - you never know what you are going to get, even with a CP download.
No idea why, but I "Trust" NuGet binaries more than CP. strange, but true.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Since you already made articles for those binaries it's enough to link to the articles and include the binaries with the source.
Otherwise I would have said you should include source for them as well.
|
|
|
|
|
You're the only one that came down on including the binaries with the source so I've decided to go with option #2 and provide instructions on setting up the build step and putting the binaries where they need to be.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Well you got three different answers.
Do what's easiest, as long as one can recreate a working project.
|
|
|
|
|
I did, and thanks for your input. Usually I find asking helps, even if it just helps lead me my own way. I get "stuck" in analysis paralysis, and asking can often "unstick" me.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: analysis paralysis
My nemesis.
|
|
|
|
|
As others have said you could make the binaries available on NuGet, but I would also include in the article a link to your previous articles that tell how to make those binaries.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
I don't know that NuGet will let me do what I need to do since these projects are not referenced binaries, but rather binaries included in the *source directory* used during a pre-build step, and not during execution.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I mean the low level protocol, not some framework, API or driver. In my ongoing quest to interface modern devices to very old 8 bit computers I have stumbled over this:
DEBO USB TTL: Raspberry Pi -USB-TTL-Schnittstellenwandler, CH340G bei reichelt elektronik[^]
Not really rocket science. With this I can send and receive bytes from a USB device with a simple UART. This would solve a few problems at once. A simple cheap memory stick would be all the hard disk' an 8 bit computer would ever need. Don't worry about speed. Mass storage is for many reasons a relatively slow affair on 8 bit computers, beginning with their low bandwith on the bus. Remember what Commodore did with the C64's floppy drives? I could also use a USB keyboard or a mouse.
So, with that converter and a UART I can now talk to USB devices. Can I also hook up a USB hub to it and access several USB devices over the same UART? How do I select devices? How do I request or send bytes? Some kind of USB protocol with an embedded device specific protocol?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I talk to it sometimes. Something along these lines: "Just get in to the slot you little..."
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
you realize they're all made overseas, they're pretty simple
... they don't understand English.
this internet has become nothing but fake news.
... time to fix it, time to get back to the fax!
|
|
|
|
|
lw@zi wrote: I talk to it sometimes. Something along these lines: "Just get in to the slot you little..."
Has it ever responded with, "wrong way - flip me over"?
|
|
|
|
|
That would be scary at first and then helpful. I can almost see another useless IoT device in the making.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
Quote: "wrong way - flip me over"? I had a girlfriend say that to me once, long, long ago.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
If this were not the place it is, I would now ask you by which coordinate axis you flipped her over and if that was the right choice.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
It was the X coord.
I really miss The Soapbox sometimes.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Whew, glad you didn't ask.
|
|
|
|
|
I was trying to be subtle...
|
|
|
|
|
Twice, ironically.
|
|
|
|
|
dandy72 wrote: Has it ever responded with, "wrong way - flip me over"?
Daily. I think my USB sticks need the Jeep warning:
If you can read this, flip me over.
|
|
|
|
|
Looks neat, I just know PS2 ports are tough, never killed one, USB on the other hand I have blown up several occasions. I haven't tried low level reading with USB, I'm guessing it standard serial (bit in, shifted, byte full?) just a higher speeds... If memory serves Microchip did do a PDF on their web site that was quite helpful also Jan Axelsons USB complete is good, try looking at Jan Axelson's Lakeview Research She is quite good with communications stuff...
|
|
|
|
|
PS/2 would be the other option for keyboard and mouse. It also uses a serial protocol, but in the lower kHz frequencies. I could probably program a PIC16FXXX to do that, but hooking up a PIC to an 8 bit bus is awkward. With 20 MHz the PIC is to slow to respond to signals on the bus in time. Still, I would try this if everything else fails. In the old days memories were to slow and had to delay the processor. Now it's slowpoky microcontrollers who need the same treatment. Nothing ever changes.
As for the mass storage: Serial ATA is a good candidate here. It's very much a direct read or write access from a 16 bit(!) bus to the drive's controller. With only an 8 bit bus things get slightly more complicated. Not that I want to dig out old obsolete hard disks. Compact flash memory cards use the serial ATA interface as well. One way or the other, I want a SSD for my old computer.
Edit: Look at this datasheet! A simple 8 bit parallel interface one one side and USB sticks or SD cards on the other. The commands to access the stick are also documented.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
modified 4-Dec-19 20:08pm.
|
|
|
|