Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
45 user(s) are online (23 user(s) are browsing Forums)

Members: 0
Guests: 45

more...

Headlines

Forum Index


Board index » All Posts (sba)




Re: SimpleMail AREXX script
Just popping in
Just popping in


Simply add a new comment to an existing Feature Request.

Go to top


Re: SimpleMail AREXX script
Just popping in
Just popping in


It will be available in 0.39. Please have a look at https://sonumina.de/jenkins/job/SimpleMail/ for latest builds for OS4.

The argument is of type /K/M.

Go to top


Re: SimpleMail AREXX script
Just popping in
Just popping in


I read this thread by accident. I enhanced SimpleMail's MAILWRITE command with an ATTACHMENT arg. I will also add an argument to command line. Both enhancements should be sufficient to fulfill the purpose you requested.

I recommend to use the feature request tracker next time as I don't regularly crawl the net about feature requests for SimpleMail ;) (even if the request is already in, you may vote for it to get my attraction).

Go to top


Re: Vs. Racing!
Just popping in
Just popping in


Quote:

Hans wrote:
BTW, GCC can actually compile Objective-C. I tried it a while back. Alas, we're missing an AmigaOS port of the Objective-C runtime libraries, so it's not much use at present. It might be worth creating a bounty for the runtime library. If there's enough interest and someone with the necessary expertise, it might happen, and would be useful for porting stuff from the MacOS/iOS world.


Seeing this thread yesterday, I tried to build an objc compiler from adtools using the new gcc 4.5.x branch. The compiler builds without problems and also a simple "Hello World" world program compiles with the generated compiler. I have no clue about the requirements of an objc runtime, but as far as I can tell from the source, the only platform specific code deals with threads. I guess this game would be a nice test candidate to see what exactly needs to be done.

Go to top


Re: DEbug 101
Just popping in
Just popping in


@kas1e
If possible, I would recommended that the development of the debugger takes place in the adtools repository, which is the standard repository for development related software for AmigaOS. With a collaborative approach, each interested dev can at least work part time on the project.

Go to top


Re: DEbug 101
Just popping in
Just popping in


@kas1e

Quote:

kas1e wrote:
@Mrodfr
Valgrind are good too, yes, but its not debugger. Its more likely "bug hunting tool", which are good to have too of course, but that is not gebugger (too different purposes). The good example of wellknown debuggers its GDB on linux and Olly on Win32.


The valgrind-framework is originally intended to be an instrumentation framework (actually, my probably never finished work doesn't provide a port of valgrind but something on top of libvex). You easily can (in theory) inject breakpoints as well and make it more interactive. It is probably not needed in the Linux world as they are decent debuggers available. The difference between the "valgrind"-approach and a normal debugger is that the "valgrind"-approach emulates the CPU while the latter runs the code directly (and thus is faster, and probably faster to code). I also think that newer version of GDB come with a CPU simulation.

Go to top


Re: Unify libraries for developers
Just popping in
Just popping in


@Varthall
Hosting the projects on central repository is a bit different, because the actual development would take place there as well. Although I personally lack the time to contribute to a project like this, I strongly recommend to coordinate the development efforts.

AmiUpdate is great for the distribution of the released devs files, though.

Go to top


Re: Cross compilation first steps
Just popping in
Just popping in


@emeck

Did you compile the cross compilers yourself or did you take precompiled binaries? There were some changes in the mean time, so it would be important to know whether you are using the most recent version of gcc of the 4.2.4 and 4.4.4 branch. Any gcc 4.4.3 is definitively obsolete.

The gcc 4.4.4 branch can be found in the branches directory of the adtools project (http://www.sf.net/projects/adtools). The gcc 4.2.4 branch is trunk at the moment. There is also a file with instructions how to compile a cross compiler (improvements to this file are very welcome). Questions regarding the process should be directed to the adtools mailing list.

After you compiled the cross compiler yourself and the problem persists, please supply a full basic example with Makefile that demonstrates the problem and post it as a bug in the adtools tracker. Thanks!

Go to top


Re: Did anyone trying to port Valgrind ever ?
Just popping in
Just popping in


Hello all,

I have tried to port valgrind myself a while ago. As it seemed to be a very difficult task (lot of #ifdef linux inside the code), I decided to start an own valgrind implementation, which is based on libvex, which is the core of valgrind, and works out of the box on amiga OS. Libvex is the part that is responsible to convert the binary code to the IR code and vice versa. I made good progress (it is possible to detect bugs for a quite limited number of instructions) but I couldn't do more than that (so a lot of work is still ahead) due to some other priorities.

If anyone is interested in helping me out please contact me by email (mail@<my domain). I can easily prepare the code and upload it to adtools project on sourceforge then, where the development should ultimately should take place.

Bye,
Sebastian

Go to top



TopTop




Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project