Jump to content

LX.NET

Members
  • Content Count

    796
  • Joined

  • Last visited

Community Reputation

329 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. Definitely a physical release first for me. Great to hear the game is almost finished
  2. 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.
  3. 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!
  4. I have replacement parts for that. PM me if interested.
  5. 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/
  6. 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.
  7. 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?
  8. 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
  9. Hyper-V shouldn't be that much of a problem, or are you running Windows 10 Home?
  10. 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
  11. 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
  12. For those working in BLL+newcc65 use this: # See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.154.2/containers/ubuntu/.devcontainer/base.Dockerfile # [Choice] Ubuntu version: bionic, focal # [Choice] Debian version: buster, stretch ARG VARIANT="focal" FROM mcr.microsoft.com/vscode/devcontainers/base:0-${VARIANT} # Install additional OS packages for build tooling and SSL libraries RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ && apt-get -y install --no-install-recommends build-essential libssl-dev RUN mkdir -p /sdk WORKDIR /sdk RUN wget http://bjoern.spruck.net/lynx/newcc65_mod.tgz RUN git clone https://github.com/42Bastian/lyxass.git RUN git clone https://github.com/42Bastian/sprpck.git RUN git clone https://github.com/42Bastian/new_bll.git RUN git clone https://github.com/42Bastian/lynx-encryption-tools.git # newcc65 RUN tar -zxvf newcc65_mod.tgz WORKDIR /sdk/newcc65 RUN make install RUN install bin/* /usr/bin # BLL ENV BLL_ROOT="/sdk/new_bll/" # lyxass WORKDIR /sdk/lyxass RUN make RUN install lyxass /usr/bin # sprpck WORKDIR /sdk/sprpck/src RUN make RUN install sprpck /usr/bin # Lynx encryption tools WORKDIR /sdk/lynx-encryption-tools #RUN make #RUN install * /usr/bin As you can see, the last two instructions have been commented out, pending a pull request for @42bs to fix the compilation of the lynxenc, lynxdec tooling
  13. @karri You might be able to find this Dockerfile content useful for creating a Dev Container with your tooling, focussing on CC65: # See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.154.2/containers/ubuntu/.devcontainer/base.Dockerfile # [Choice] Ubuntu version: bionic, focal # [Choice] Debian version: buster, stretch ARG VARIANT="stretch" FROM mcr.microsoft.com/vscode/devcontainers/base:0-${VARIANT} # Install additional OS packages for build tooling and SSL libraries RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \ && apt-get -y install --no-install-recommends build-essential libssl-dev RUN mkdir -p /sdk WORKDIR /sdk RUN git clone https://bitbucket.org/atarilynx/lynx.git WORKDIR /sdk/lynx/tools RUN make -f Makefile.deb WORKDIR /sdk/lynx/tools/cc65 RUN make -f make/gcc.mak install Paste that when you added the Remote container files and it should build a container with your tooling available. Anyone using sprpck, please let me know. It will need some additional instructions to build the image
  14. @Karri, I have tried to get a new Dockerfile that uses your atarilynx repository to build the newcc65 source code. This time I chose for Ubuntu (focal version), to experiment with another Linux distribution than Alpine. I am getting a couple of errors when I try to compile cc65 (from newcc65) and ra65: vscode ➜ /sdk/lynx/tools/newcc65 (master ✗) $ sudo make install make[1]: Entering directory '/sdk/lynx/tools/newcc65/cc65' gcc -O3 -Wall -ffast-math -fomit-frame-pointer -c -o expr1.o expr1.c In file included from expr1.c:16: code-65.h:45:15: error: unknown type name ‘intptr_t’ 45 | void immedgbl(intptr_t i); | ^~~~~~~~ expr1.c: In function ‘op_assoc’: expr1.c:452:11: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 452 | return ((int)ops->gen); | ^ expr1.c: In function ‘hie_internal’: expr1.c:482:16: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 482 | if ( (gen = (void *)op_assoc((this_tok = curtok), ops)) ) | ^ make[1]: *** [<builtin>: expr1.o] Error 1 make[1]: Leaving directory '/sdk/lynx/tools/newcc65/cc65' make[1]: Entering directory '/sdk/lynx/tools/newcc65/ra65' gcc -pipe -O3 -fomit-frame-pointer -Wall -DUNIX -s -o xgen.o -c xgen.c xgen.c: In function ‘frag_gen_size’: xgen.c:472:7: warning: suggest explicit braces to avoid ambiguous ‘else’ [-Wdangling-else] 472 | if (offset > 124) /* too big? */ | ^ xgen.c: In function ‘init_gen’: xgen.c:928:24: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 928 | segment[3].objsize = (int) | ^ xgen.c:929:19: error: lvalue required as left operand of assignment 929 | segment[0].base = | ^ xgen.c: In function ‘out16’: xgen.c:151:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result] 151 | write(output_fd, two_bytes, 2); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ xgen.c: In function ‘out8’: xgen.c:158:3: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result] 158 | write(output_fd, two_bytes, 1); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ make[1]: *** [makefile:26: xgen.o] Error 1 make[1]: Leaving directory '/sdk/lynx/tools/newcc65/ra65' make[1]: Entering directory '/sdk/lynx/tools/newcc65/runtime' ra65 runtime.m65 I also had to remove the -m486 flags for the gcc compiler. Can we fix these errors (and warnings)? Are you getting these too? Also, would it be an idea to separate the newcc65 repo out of the big atarilynx repo as well so we can compose a different toolchain by combining bll, newcc65, sprpck, lyxass from the latest version (in addition to the frozen toolchain inside atarilynx repo)?
  15. I will use a combination of Karri's repo and BLL from your GitHub then. Anyone have a less than trivial source code project to compile against newcc65 and BLL? Lordkraken perhaps?
×
×
  • Create New...