Jump to content

LX.NET

Members
  • Content Count

    800
  • Joined

  • Last visited

Community Reputation

330 Excellent

About LX.NET

  • Rank
    Dragonstomper
  • Birthday 10/15/1971

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    The Netherlands
  • Currently Playing
    Bill and Ted's Excellent Adventure
  • Playing Next
    Xenophobe and Shanghai

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Sprite structures cannot be transposed like that as their data structure is heavily dependent on the bits in the sprite data.
  2. That is awesome! Really impressive and almost tangible to see those executions, reads and writes
  3. @karri You should be able to setup it whichever way you want. That might mean tweaking your dockerfile to suit your needs. I assume you have already done that. The sources to build the tooling is included at the moment. It can be optimized to be removed in a final docker image. That would leave just the tooling and your game code. If you want we can arrange a Teams or Zoom session to dive in with screen sharing. It will probably help getting details across. Let me know who is interested so we can try and set up a meeting.
  4. Definitely a physical release first for me. Great to hear the game is almost finished
  5. Wonderful graphics and nice backgrounds. I would reconsider the third from the top. It seems to be noise and more difficult to distinguish real tiles from background. Second one seems out of place in terms of color. Keep up the good work. Greatню to see the progress.
  6. LX.NET

    Growing Ties

    Really cool. Looking forward to the new release and the physical one as well. Nice to see the bonus games are going to be included!
  7. I have replacement parts for that. PM me if interested.
  8. A week ago I updated the setup of a Windows-based device to use Visual Studio 2019, with new instructions to get it to work, new screenshots and a new HelloWorld version that is compatible with the latest CC65 version. Hope you like it. https://atarilynxdeveloper.wordpress.com/2012/04/07/programming-tutorial-part-2development-environment/
  9. I updated the Windows based setup to refer to VS2019. https://atarilynxdeveloper.wordpress.com/2012/04/07/programming-tutorial-part-2development-environment/ PLease let me know what you think of the new article and whether it is more helpful. Any questions, feel free to ask.
  10. Who is the owner of newcc65? It would be good to also have that in a public place (as stated in the dev-containers thread as well). Is that yours, @42bs and would you be willing to host it in your GitHub repo?
  11. A Docker file is a description to build an image. This is a one-time activity that is performed by the tooling. Afterwards, a container instance is started based on the image. It has resemblances to a Virtual Machine (container instance) and its VM image (container image). There are crucial differences between VMs and containers however. VMs offer hardware virtualization, where containers do software virtualization. The case for containers is that it allows a developer to have its own source code for the Atari Lynx project and the toolchain he/she is using as well. If you having a container image (or the Docker file that produced it) allow a frozen toolchain that can be reproduced many years later. Having said that, the current Docker files I showed earlier get the latest sources of the tooling and compiles it. This means they are not frozen, but provide an always up-to-date toolchain when the image is rebuild. We could choose to create and share a docker image in a public place, much like GitHub (it could be Docker Hub for example). Then a developer could download a Docker image (e.g. CC65:2.19, or newcc65:feb2021) and have a frozen toolset. The container is containing all of the tools and is very lightweight when compared with VM images. It is a security boundary and doesn't 'contaminate' your system. In other words, you can easily run multiple containers with different versions of the toolchain side-by-side. Karri could have his own CC65 2.13 stack and still look at code that I am building on 2.19, without having to reinstall it on his development machine. It comes with my code and in a container that can be thrown away. Hopefully this helps a little to get a better understanding of the possibilities. I will create a repository at github to hold Docker files for environments. Probably something like https://www.github.com/AtariLynx/devcontainers. Alex
  12. Hyper-V shouldn't be that much of a problem, or are you running Windows 10 Home?
  13. Thanks for accepting the pull request, @42bs I will update the container image. On another note: I saw that the environment variables for CC65INCLUDE and CC65LIB are not set in the container image yet. Also, there seem to be some errors in building the newcc65 source code for libsrc. Perhaps @sage can help here. I will report the errors later today. Tackling this, we can also use c code from newcc65. Right now, I have been able to successfully build .asm with lyxass, and use the tooling for lynxenc and lynxdec. Almost there. I would appreciate some feedback on whether all libs and executables are in their proper place. Not a Linux person, so do not have a clue whether it is okay. Thanks
  14. It would be good to confirm two things: Are the changes made by @sage in lyxass covered in the newer version by @42bs? Can we put @sage's newcc65 sources in a Git repo (do you have a Git repo somewhere or should we put it at github.com/42Bastian for example?) Alex
×
×
  • Create New...