a patch would work. Another option would be to have the indicator work from the status bit when on auto, but if you click the tcc on button it overrides and turns the indicator on and vice versa for the tcc off button.
Printable View
compiled against 5.6. It works on linux!!!!
I compiled eehack 3.5 and it connected with no error.
I'd like to try to compile 4 if at all possible.
holy $#*()^ brian!!! awesome!Quote:
compiled against 5.6. It works on linux!!!!
there's like zilch for tuning tools in linux besides megasquirt afaik, this is groundbreaking, since tunerpro non-rt runs so well in wine, it's likely that full-time linux users can tune their LT1s now.
im a bit worried about delay timing since i've 'tuned around' windows timers being shoddy, so i'll be interested to see if everything works alright.
how does it look appearance-wise? can you screenshot it?
so this thing is totally independant of the tcc enable routine that sets the flag. this is no big deal, im going to release with a note in the tooltip informing the user. i've decided i dont want to 'light up the light' falsely, since that wont match what's in the log, and wont play back properly. i'd have to falsify data in the datastream, which i can do, but is against my design principles, i want my data to be saved to disk completely unmodified.Quote:
a patch would work. Another option would be to have the indicator work from the status bit when on auto, but if you click the tcc on button it overrides and turns the indicator on and vice versa for the tcc off button.
so is what it is until i patch it later, but no more patches in this release.
trying to compile 4, but It's currently failing
I get the same error compiling 4 with both qt5.5 and 5.6Code:-I. -I. -I../../Qt5.6.0/5.6/gcc_64/mkspecs/linux-g++ -o flash_routine.o flash_routine.cpp
In file included from datastream.h:7:0,
from mainwindow.h:12,
from flash_routine.cpp:3:
config.h:35:0: warning: ignoring #pragma warning [-Wunknown-pragmas]
#pragma warning(disable: 4100)
^
flash_routine.cpp: In member function ‘void mainWindow::writeflash()’:
flash_routine.cpp:343:3: error: jump to label ‘FLASH_WRITE_CLEANUP’ [-fpermissive]
FLASH_WRITE_CLEANUP:
^
flash_routine.cpp:84:12: note: from here
goto FLASH_WRITE_CLEANUP;
^
flash_routine.cpp:94:7: note: crosses initialization of ‘int write_post_delay’
int write_post_delay = 70;
^
flash_routine.cpp:91:8: note: crosses initialization of ‘bool enable_compression’
bool enable_compression = ui->flash_compress->isChecked();
^
flash_routine.cpp:343:3: error: jump to label ‘FLASH_WRITE_CLEANUP’ [-fpermissive]
FLASH_WRITE_CLEANUP:
^
flash_routine.cpp:66:10: note: from here
goto FLASH_WRITE_CLEANUP;
^
flash_routine.cpp:94:7: note: crosses initialization of ‘int write_post_delay’
int write_post_delay = 70;
^
flash_routine.cpp:91:8: note: crosses initialization of ‘bool enable_compression’
bool enable_compression = ui->flash_compress->isChecked();
^
flash_routine.cpp: In member function ‘void mainWindow::readflash()’:
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
FLASH_READ_CLEANUP:
^
flash_routine.cpp:439:10: note: from here
goto FLASH_READ_CLEANUP;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
FLASH_READ_CLEANUP:
^
flash_routine.cpp:435:10: note: from here
goto FLASH_READ_CLEANUP;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
FLASH_READ_CLEANUP:
^
flash_routine.cpp:426:10: note: from here
goto FLASH_READ_CLEANUP;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
FLASH_READ_CLEANUP:
^
flash_routine.cpp:422:10: note: from here
goto FLASH_READ_CLEANUP;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
FLASH_READ_CLEANUP:
^
flash_routine.cpp:417:10: note: from here
goto FLASH_READ_CLEANUP;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:501:3: error: jump to label ‘FLASH_READ_CLEANUP’ [-fpermissive]
FLASH_READ_CLEANUP:
^
flash_routine.cpp:409:10: note: from here
goto FLASH_READ_CLEANUP;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:520:3: error: jump to label ‘FLASH_READ_CLEANUP_NO_RST’ [-fpermissive]
FLASH_READ_CLEANUP_NO_RST:
^
flash_routine.cpp:406:10: note: from here
goto FLASH_READ_CLEANUP_NO_RST;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:520:3: error: jump to label ‘FLASH_READ_CLEANUP_NO_RST’ [-fpermissive]
FLASH_READ_CLEANUP_NO_RST:
^
flash_routine.cpp:402:10: note: from here
goto FLASH_READ_CLEANUP_NO_RST;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
flash_routine.cpp:520:3: error: jump to label ‘FLASH_READ_CLEANUP_NO_RST’ [-fpermissive]
FLASH_READ_CLEANUP_NO_RST:
^
flash_routine.cpp:393:12: note: from here
goto FLASH_READ_CLEANUP_NO_RST;
^
flash_routine.cpp:451:7: note: crosses initialization of ‘int read_floor’
int read_floor = 0x0D80;
^
Makefile:10022: recipe for target 'flash_routine.o' failed
make: *** [flash_routine.o] Error 1
brian@linux-w1cw:~/Downloads/eehack-master>
ah, weird, must be a gcc-specific error. i can fix that, though. we just need to move the initializers further up in the function to shut it up (or i could improve my logic so there's no GOTOs in that function, but im lazy and they work fine)
That would probably be the best solution, but for now I got it to compile adding -fpermissive to the flags
Attachment 10065
at least I can test it on my way to work in the morning
brian i've committed a change to my git repository that should fix that compilation issue for you.
patch
https://github.com/resfilter/eehack/...b6bd08c803800c
new tarball
https://github.com/resfilter/eehack/archive/master.zip
c++ is really sloppy. im so used to ANSI c, then c++ does stuff like let me initialize variables in a loop. it really increases potential variable scope complexity.. then makes a GOTO freak out.
i'm done with this release for sure. it's good to go. enjoy!
http://fbodytech.com/eehack-4-0-released/
well, compiled with no issue, connected with no issue, datalogged with no issue! Next test.... flashing.
Only issue is saving the log file, and I expect possibly saving any type of file. There seems to be an issue with file extensions on linux. If you don't manually type an extension then it saves without one. I have this same behavior on datamaster under wine.
Not a huge deal, if you are aware of the behavior. Just have to type it every time. I guess that possibly setDefaultSuffix(const QString & suffix) could be used, but not sure if it will work. I'll do some testing this evening. So far so good though!
Attachment 10067
hmm
about the file extension issue. Reading QT documentation, I see this:
So windows native dialog is probably dealing with the suffix, and since it is not specified QFileDialog isn't?Quote:
QFileDialog::getSaveFileName
On Windows, and OS X, this static function will use the native file dialog and not a QFileDialog.
Just thinking out loud here.
i can fix that.
i should get a virtual machine going and try this out
Awesome!
I compiled it against the 5.6 beta release located here:
http://download.qt.io/development_re....6/5.6.0-beta/
and let me just state how fantastic it is to have this as a native binary running on linux!
Really stoked about that.